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

Support for repository_url and vcs_url in purl field #20

Closed
vaaralav opened this issue May 28, 2019 · 2 comments
Closed

Support for repository_url and vcs_url in purl field #20

vaaralav opened this issue May 28, 2019 · 2 comments

Comments

@vaaralav
Copy link
Contributor

It would be great if packages that are installed from non-NPM origin had the information in their purl.

For example

npm install git+ssh://git@github.com:npm/cli.git#v1.0.27

Would create a component with purl pkg:npm/cli@1.0.27?vcs_url=git+git+ssh://git@github.com:npm/cli.git#v1.0.27

Similarly repository_url could be added for packages installed from custom registries.

@stevespringett
Copy link
Member

Do you know of a way that npm will return the repo in which the component was resolved from?

For example, an org has an internal Artifactory or Nexus repo they resolve all npm components from. CycloneDX would need to be able to identify the components that are accessible in the public npm repo (even if they also exist in a private repo) from the components that only reside in an alternate repo (artifactor/nexus or some other non-npm repo).

@jkowalleck
Copy link
Member

this feature was implemented in https://github.com/CycloneDX/cyclonedx-node-npm/
please switch to the NPM flavour of this package.

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

No branches or pull requests

3 participants