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

dotnet list package --vulerable should support auditSources #13767

Open
zivkan opened this issue Sep 4, 2024 · 0 comments · May be fixed by NuGet/NuGet.Client#6206
Open

dotnet list package --vulerable should support auditSources #13767

zivkan opened this issue Sep 4, 2024 · 0 comments · May be fixed by NuGet/NuGet.Client#6206
Assignees
Labels
Area:NuGetAudit Functionality:ListPackage dotnet.exe list package Priority:2 Issues for the current backlog. Type:DCR Design Change Request

Comments

@zivkan
Copy link
Member

zivkan commented Sep 4, 2024

NuGet Product(s) Affected

dotnet.exe

Current Behavior

dotnet list package --vulnerable was created before NuGetAudit or auditSources. It still only reports vulnerabilities when the source's package metadata ("registration") endpoint reports the vulnerability. When a project has a lot of packages (especially transitive packages and `--include-transitive is used), the command can take a long time while many HTTP requests are made.

Desired Behavior

If NuGetAudit reports a vulnerability during restore, then dotnet list package --vulnerable --include-transitive should report it too, even if none of the package sources have vulnerability data, but an audit source is defined.

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area:NuGetAudit Functionality:ListPackage dotnet.exe list package Priority:2 Issues for the current backlog. Type:DCR Design Change Request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants