include a GitHub workflow for vulnerability scanning #1075
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
alexanderpann
force-pushed
the
feature/enable_vulnerability_scanning
branch
from
19e31db to
db1964d
Compare
sergej-koscejev
approved these changes
Dec 4, 2024
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.
Currently, the build won't fail. We would have to add an argument like --failOnCVSS 7 to fail the build for issues with high severity. For example, for jgraphx we would have to add it as a false positive since we can't update the library.
You can find the output for a run on the actions page: https://github.com/JetBrains/MPS-extensions/actions/runs/12163684040?pr=1075. There is an artifact Depcheck report.
Alternativelly, we could only add it for the
workflow_dispatchevent. Then you would have to call it manually.