Repository navigation
Add glsec to Supply chain specific tools - #129
Open
predictor2718 wants to merge 1 commit into
Open
predictor2718 wants to merge 1 commit into
predictor2718 wants to merge 1 commit into
Conversation
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds glsec to the Supply chain specific tools section. The section has no tool yet that checks the CI pipeline definition itself.
glsec is a static security linter for GitLab CI/CD pipelines. It checks
.gitlab-ci.ymlfor mutable image tags,curl | bash, hardcoded secrets, variable injection and similar issues, with 85 rules mapped to the OWASP Top 10 CI/CD Security Risks and CWE. Output formats include SARIF, JUnit and GitLab Code Quality.Disclosure: I maintain glsec.
Row: