DJC: Store Dependencies as Packages and support multiple dependency types in the DejaCode model #11
Labels
design needed
Design details needed to complete the issue
enhancement
New feature or request
help wanted
Extra attention is needed
HighPriority
High Priority
integration
Integration with other applications
major
Significant level-of-effort
vulnerabilities
Vulnerability Management
Milestone
We should store Dependencies as Packages in DejaCode. Also, in addition to simply creating Product Packages, we really need to provide the necessary qualifiers for Dependencies, especially whether they are declared as required or optional. Needs design. The processes that import Product Inventory Items from ScanCode results, or from an SBOM that provides dependency details, need to be enhanced as well as the model and the corresponding UI presentation in DejaCode.
As we do for Package, the Dependency model should be aligned with the ScanCode-toolkit and ScanCode.io ones:
Note that this improvement would enhance both license compliance and vulnerability management processes in DejaCode.
The text was updated successfully, but these errors were encountered: