DependencyTrack / DependencyTrack/dependency-track
Different Package Manager show different results
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
I am using Qt 6.4.2 from github and wrote the purl manually and got this:
`pkg:github/qt/qt5@6.4.2`
This only shows that the version is outdated, but 0 vulnerabilities
but if I use a different package manager, for example conan:
`pkg:conan/qt@6.4.2`
This has different results and shows me and 11 vulnerabilities.
What is causing the difference for the same version, but different package manager?
### Steps to Reproduce
1. Use `pkg:github/qt/qt5@6.4.2`
2. Use `pkg:conan/qt@6.4.2`
### Expected Behavior
I am expecting the same results for the same version, the package manager shouldn't have any influence in the result.
### Dependency-Track Version
4.12.2
### Dependency-Track Distribution
Container Image
### Database Server
N/A
### Database Server Version
_No response_
### Browser
Microsoft Edge
### 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.