Open
Conversation
Signed-off-by: Yu Ishikawa <yu-iskw@users.noreply.github.com>
Contributor
Author
|
@TylerJang27 I am sorry for bothering you, but I want to support other security tools besides trivy because of the recent incedents. It would be good to support alternatives in trunk. We have the two failed workflows. However, the errors don't look related to the changes. Should we open another pull request to fix them? https://github.com/trunk-io/plugins/actions/runs/23417421235/job/68115530526?pr=1123 https://github.com/trunk-io/plugins/actions/runs/23417421235/job/68115523251?pr=1123 |
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
1 participant
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.
Summary
Adds support for Grype as a new security-focused linter for vulnerability scanning across filesystems and lockfiles.
Changes
linters/grype/plugin.yamldefining thegrypetool and linter, configured to output SARIF and use a shared cache for its vulnerability database (GRYPE_DB_CACHE_DIR).linters/grype/grype.test.tsand test fixturelinters/grype/test_data/Gemfile.lockto verify vulnerability detection.tests/driver/driver.tsandtests/utils/index.tsto supportTRUNK_CACHEandXDG_CACHE_HOMEenvironment variables, ensuring proper sandboxing and caching of tool-specific data (like Grype's DB) during tests.README.mdto include Grype in the list of supported security linters.Closes #1122.