Repository navigation
Scan Cargo.lock with OSV-Scanner - #202
Merged
Merged
Conversation
cargo-audit only reads the RustSec database, so advisories that crate maintainers publish as GitHub security advisories can go unnoticed. OSV covers both. Same job as dnp3's security workflow (stepfunc/dnp3#451).
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.
Makes the security workflow symmetric with dnp3's (stepfunc/dnp3#451).
cargo auditonly reads the RustSec database, so an advisory a crate maintainer publishes only as a GitHub security advisory goes unnoticed (dnp3 had one: GHSA-6g2r-675j-hx59 inxxhash-rust, not in RustSec). The newosv-scannerjob scansCargo.lockagainst OSV, which covers both.The job is identical to dnp3's: same triggers as the
cargo auditjob, verdict taken from the JSON report, a run without a valid report reported as a tool failure rather than a finding, report uploaded, image pinned by digest (ghcr.io/google/osv-scanner:v2.6.0). The only difference isactions/checkout@v7, matching the rest of this workflow.Locally, OSV-Scanner finds no vulnerabilities in rodbus's current
Cargo.lock(198 packages).