Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature spec for suppressing specific vulnerabilities #12921

Merged
merged 6 commits into from
Mar 8, 2024

Conversation

zivkan
Copy link
Member

@zivkan zivkan commented Oct 5, 2023

view rendered spec

Note: I don't expect this to get implemented particularly soon, and I'm not going to have a lot of capacity to make frequent updates to this spec, in case it gets a lot of feedback. But I'm putting it out there now, so it has time to get sufficient feedback before it gets accepted.


## Prior Art

<!-- What prior art, both good and bad are related to this proposal? -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When thinking about prior art we can draw inspiration from, consider GitHub dependabot suppressions, CG suppressions, NPM. It will be interesting to see the granularity that each solution provides (per package, per project, per advisory, etc.). Assuming that NuGet users already have experience using those other vuln suppression mechanism, they likely expect a similar customer experience from NuGet.

accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
@advay26 advay26 marked this pull request as ready for review February 20, 2024 21:53
@advay26 advay26 requested a review from a team as a code owner February 20, 2024 21:53
Copy link
Member Author

@zivkan zivkan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only two minor things, otherwise lgtm!

accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
Copy link
Member Author

@zivkan zivkan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since I created this PR, GitHub won't let me approve it, but it LGTM now.

accepted/2023/NuGetAudit-supress-advisory.md Outdated Show resolved Hide resolved
@advay26 advay26 merged commit 344db7e into dev Mar 8, 2024
1 check passed
@advay26 advay26 deleted the zivkan-NuGetAudit-Supressions branch March 8, 2024 21:45
@advay26 advay26 restored the zivkan-NuGetAudit-Supressions branch March 8, 2024 21:45
@anangaur
Copy link
Member

It's easy to forget about suppressions done in a config file that's not in your face. Are we thinking about some messaging (info) to state that? Like as part of restore, something like: "Note: Some warnings due to packages having vulnerabilities have been suppressed. See , for a list of those suppressions."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants