Repository navigation
Audit dependencies daily, and scan them with OSV-Scanner - #8
Merged
Merged
Conversation
The audit job ran only with CI, and only against RustSec, which has no entry for GHSA-qwgh-2vcv-g2f7 (block-buffer). It moves to a Security Audit workflow, as in rodbus and dnp3, which also runs daily and adds an osv-scanner job reading GitHub security advisories. Both jobs generate the lockfile first, since it isn't committed, and take their verdict from the JSON report, so a tool or network failure isn't reported as a finding. The audit job keeps its name, so the required check still matches. The release workflow no longer runs it.
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.
The audit job ran only with CI, and only against RustSec, which has no
entry for GHSA-qwgh-2vcv-g2f7 (block-buffer). It moves to a Security Audit
workflow, as in rodbus and dnp3, which also runs daily and adds an
osv-scanner job reading GitHub security advisories. Both jobs generate the
lockfile first, since it isn't committed, and take their verdict from the
JSON report, so a tool or network failure isn't reported as a finding.
The audit job keeps its name, so the required check still matches. The
release workflow no longer runs it.