DependencyTrack / DependencyTrack/frontend
Highlight vulnerable packages in the dependency graph.
- Dominant language
- Vue
- Stars
- 171
- Forks
- 250
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 84
Description
### Current Behavior
It is currently impossible to determine exactly which of our own packages introduced a vulnerable package.
On the vulnerability audit page, the "Show in dependency graph" button sometimes causes the browser to fail.
### Proposed Behavior
I would like to see directly in the dependency graph which packages have dependencies; since dependencies can be multi-layered, I cannot intuitively see which of the packages my own software depends on contains a vulnerability.
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/main/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/frontend/issues) for whether this enhancement was already requested
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the vulnerability audit page and follow the “Show in dependency graph” flow, then inspect the dependency graph rendering entry point it reaches. Done means vulnerable packages are visibly identified in the graph, including through multi-layer dependencies, and the audit-page action no longer causes the browser to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100