Add dependency vulnerability checks - #361
Merged
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
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.
High- and critical-severity package advisories do not currently block pull requests. Add two independent, SHA-pinned checks: GitHub Dependency Review rejects newly introduced vulnerable dependencies, and a full-solution NuGet restore audits direct and transitive packages with high/critical advisories treated as errors. Audit-source failures also fail the NuGet job, while the existing build/test job remains independent.
The NuGet audit uses nuget.org's vulnerability-data source and runs with the SDK pinned by
global.json.Validation: full-solution
dotnet restore -p:AuditPipeline=true --forcepassed locally using the available .NET 10.0.201 SDK; the CI job installs the repo-pinned 10.0.401 SDK. The XML and workflow YAML parse, and the audit MSBuild properties evaluate as intended.After these checks pass on this PR, add their observed GitHub Actions check names to the existing strict
masterruleset.