Api Key Leaks: Add Trivy to tools section #547
Merged
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 will add Trivy to the tools section of the topic
Api Key Leaks
. This is currently my go-to tool to scan docker images or repositories for secrets and therefore should be mentioned. As I could not see it mentioned somewhere, I picked this topic as it seemed to fit best. But it might also fit for other topics such as scanning for vulnerable dependencies (CVE) used in a projects or weaknesses in regards of SBOM/IaC. If you see a better fit for Trivy at other topics or might want to add it redundantly multiple times I guess we could add it to this MR.Let me know what you think. :)
(Also changed the phrasing for two other tools as their main repository uses the upper/lowecase as changed which should not require a separate MR)