DependencyTrack / DependencyTrack/dependency-track
Integrate check against OSSF Malicious Packages List
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
Currently we track Vulnerabilities of components. However, there are cases where malicious packages made it into repositories, either by taking over existing projects, abusing accounts or by typo-squatting or similar techniques, which might not be covered by typical vulnerability databases.
### Proposed Behavior
OpenSSF provides a project with known malicious packages at https://github.com/ossf/malicious-packages. Dependency-Track could integrate their data to identify and flag malicious packages.
### 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
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository structure and the linked OpenSSF Malicious Packages project to locate existing vulnerability-data integrations; done means the requested malicious-package data is integrated and packages can be identified and flagged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100