pass-enoaudit flag passes integration even without registry returning ENOAUDIT
See original GitHub issueTest:
pass-enoaudit: true
critical: true
Expected Behavior: If registry does not return ENOAUDIT, the expected behavior is the integration fails with error
"vulnerabilities": {
"info": 0,
"low": 18,
"moderate": 47,
"high": 402,
"critical": 1
}
Failed security audit due to critical vulnerabilities.
Exiting...
Current Behavior: Registry is not returning ENOAUDIT and audit-ci passes the integration even with critical vulnerabilities
"vulnerabilities": {
"info": 0,
"low": 18,
"moderate": 47,
"high": 402,
"critical": 1
}
ACTION RECOMMENDED: An audit could not performed due to 5 audits that resulted in ENOAUDIT. Perform an audit manually and verify that no significant vulnerabilities exist before merging.
Passed npm security audit.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
29 - Stack Overflow
`npm audit` keeps returning "Your configured registry (https://registry.npmjs.org/) does not support audit requests.". How do I make it work ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fix is to change line 27 in lib/audit.js to if (config[‘pass-enoaudit’] && message.includes(RETRY_ERROR_MSG[pm])) {
Closed with #108