DependencyTrack / DependencyTrack/dependency-track
Ability to scope components/vulnerabilties
Open
enhancement
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
When used by multiple teams, it is important to be able to understand what applies to the set of projects they are responsible for. So, being able to establish "scope" results in other views (i.e. component and vulnerability views) to a subset of projects (which might be established by ACL or search or something else)
There are clearly different ways of achieving this so I'll try to be implementation agnostic. But the basic idea is that there are only a subset of the projects I am interested in, so I'd like to only have to look through results that apply to those projects.
Contributor guide
Assessment
This issue has not been assessed yet.