DependencyTrack / DependencyTrack/dependency-track
OSS Index does not analyze components whose versions include v prefix
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
Dependency-Track currently fails to analyze multiple Composer components through OSS Index when the version string includes a leading v (e.g., v6.4.4, v1.3.0, etc.).
Example component that cannot be analyzed: https://ossindex.sonatype.org/component/pkg:composer/symfony/security-http@v6.4.4
After investigation, this appears to be caused by the open bug:
[#5197](https://github.com/DependencyTrack/dependency-track/pull/5197) (fix not yet merged)
### Impact:
There is a large number of Composer components whose versions include the v prefix.
For all of them:
- OSS Index does not return vulnerabilities
- Dependency-Track reports them as having “no vulnerabilities”
- This results in unreliable or incomplete vulnerability visibility.
### Steps to Reproduce
1. Create a new project
2. Add for example, any Symfony component like pkg:composer/symfony/security-http@v6.4.4
3. No vulnerabilities detected, when Sonatype says there are. https://ossindex.sonatype.org/component/pkg:composer/symfony/security-http@v6.4.4
### Expected Behavior
Vulnerabilities properly detected when using OSS Index analysis
### Dependency-Track Version
4.13.5
### Dependency-Track Distribution
Container Image
### Database Server
PostgreSQL
### Database Server Version
_No response_
### Browser
Google Chrome
### 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 defect was already reported
Contributor guide
Assessment
This issue has not been assessed yet.