Skip to content

x/vulndb: add a lint check for unmerged modules #69118

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

Open
tatianab opened this issue Aug 28, 2024 · 1 comment
Open

x/vulndb: add a lint check for unmerged modules #69118

tatianab opened this issue Aug 28, 2024 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo

Comments

@tatianab
Copy link

Add a lint check for vulndb reports to ensure that if modules can be merged (they have the same module and packages, but possibly distinct versions), then they are merged. This will make it less likely for us to submit UNREVIEWED reports that incorrectly mark an entire module as vulnerable.

@tatianab tatianab added the vulncheck or vulndb Issues for the x/vuln or x/vulndb repo label Aug 28, 2024
@tatianab tatianab self-assigned this Aug 28, 2024
@gopherbot gopherbot modified the milestones: Unreleased, vuln/unplanned Aug 28, 2024
@tatianab tatianab removed their assignment Mar 6, 2025
@JunyangShao JunyangShao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Mar 7, 2025
@JunyangShao
Copy link
Contributor

@golang/vulndb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Projects
None yet
Development

No branches or pull requests

3 participants