DependencyTrack / DependencyTrack/dependency-track
Propagate vulnerabilities from child project to parent
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
I searched open and closed issue and didn't find anything matching. I use release of one project as a dependency in another project.
### Current Behavior:
So, project a is tracked with its dependencies in DT.
Project b has its dependencies inventorized and one of its dependency is project a. Project b does not get vulnerability information from project a. Because the component "project b" does not resolve to the project b in DT.
### Proposed Behavior:
I suggest that it is already kind of possible to do that, if you would set up a mechanism that creates a matchable component in DT to every project release. Furthermore you need to set CPE that would be resolved by the internal database and update the vulnerabilities to that matchable component as vulnerabilities are discovered in the corresponding project.
DT should provide a mechanism to set a component to an internal DT project, without hacking it manually.
Contributor guide
Assessment
This issue has not been assessed yet.