You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DependencyTrack is configured to use multiple sources for vulnerability information; one of which is OSSI.
If access to OSSI fails for whatever reason (e.g. rate limit - but also like #2857), no sonatype-* vulnerabilities are reported for that project.
In this case, you can have to projects with identical components - but a complete different list of vulnerabilities.
Apparently there is no way for a user to detect if vulnerability matching was complete/successful for all sources.
Proposed Behavior
Add a status field to the project properties where it is visible whether errors were encountered during vulnerability matching.
This allows the user to actually trust the list of vulnerabilities - and know where they might be incomplete.
Current Behavior
DependencyTrack is configured to use multiple sources for vulnerability information; one of which is OSSI.
If access to OSSI fails for whatever reason (e.g. rate limit - but also like #2857), no sonatype-* vulnerabilities are reported for that project.
In this case, you can have to projects with identical components - but a complete different list of vulnerabilities.
Apparently there is no way for a user to detect if vulnerability matching was complete/successful for all sources.
Proposed Behavior
Add a status field to the project properties where it is visible whether errors were encountered during vulnerability matching.
This allows the user to actually trust the list of vulnerabilities - and know where they might be incomplete.
Checklist
The text was updated successfully, but these errors were encountered: