Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

package meta data - version_normalized #142

Open
sonnenkindhope opened this issue Jun 21, 2023 · 0 comments
Open

package meta data - version_normalized #142

sonnenkindhope opened this issue Jun 21, 2023 · 0 comments

Comments

@sonnenkindhope
Copy link

Hei hei,

what I'm trying to do
I'm trying to use Nexus as a repository in OWASP Dependency-Track.
The packages to be analyzed are stored as composer-hosted packages. It's code in a zip and uploaded to the relevant endpoint.
The packages are solely created for private use and cannot be provided using another repository.

Everything works fine getting the meta data using the route composer-hosted/p/%package%.json
With %package% just as a placeholder for the real name.

What feature or behavior is this required for?
But dependency track expects the value-pair with key version_normalized for version comparison functionalities which does not seem to be created while creating the %package%.json itself.

Is there anything I'm missing which prevents the creation of the version_normalized information? Do I interpret the value-pair wrong?

solution? (maybe, kinda...)
Since version and version_normalized may but don’t need to be different, an easy way could be to provide the value for version also in version_normalized. In doing so the provided meta data would be more like the meta data provided by e.g packagist.
As far as I understand everything seems to boil down to the functions in ComposerJsonProcessor.java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant