feat: Add osv-scanner to unit tests #1170
Merged
Conversation
This file contains 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.
OpenSSF best practices suggest using a static analysis tool to scan for known vulnerabilities.
- What I did
Added osv-scanner
- How I did it
As with atsign-foundation/at_server#1664
osv-scanner is being installed using
go install(having first installed golang itself withactions/setup-go)This is done (rather than using the OSV Scanner GitHub Action) to ensure that the pubspec.lock files are in place, which happens when we
dart pub getas part of unit tests.- How to verify it
We will have to wait for a known vulnerability to confirm that the tests fail.
- Description for the changelog
feat: Add osv-scanner to unit tests