DependencyTrack / DependencyTrack/dependency-track

Provide information on incomplete vulnerability matching for project

Open
#2,865 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
4.2k
Forks
811
Avg merge
8h 39m
Merged PRs (30d)
237

Description

### 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 https://github.com/DependencyTrack/dependency-track/issues/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

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this enhancement was already requested

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.