Issue #4119 Security Check Added #4120
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Hey @walterbender , do review this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR :- introduces an automated security check by integrating npm audit into the CI/CD pipeline. The enhancement ensures that installed npm packages are scanned for vulnerabilities, providing detailed reports on critical, high, and moderate issues. The pipeline is configured to fail if vulnerabilities are detected, enforcing secure code practices. For flexibility, a SKIP_AUDIT_FAILURE environment variable allows the pipeline to continue if needed, enabling quick iterations while still flagging security concerns. This implementation aligns with best practices, improves security posture, and reduces the risk of deploying code with known vulnerabilities.
closes #4119