We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
repository
https://github.com/CycloneDX/cyclonedx-node-npm/releases/edit/v1.19.2 introduced a fix
CycloneDX externalReferences for vcs type (#1198 via #1202)
externalReference
vcs
this was a quick fix to a larger problem: NPM manifest's repository is not guaranteed to be a URL. see https://docs.npmjs.com/cli/v10/configuring-npm/package-json#repository
The URL should be a publicly available (perhaps read-only) URL that can be handed directly to a VCS program without any modification.
so valid values could be like git@gitlab.example.com:user/project.git.
git@gitlab.example.com:user/project.git
the shortcuts with alternative protocols (github:, gitlab:, etc) are out of scope, they are expected to be normalized before processing.
github:
gitlab:
The text was updated successfully, but these errors were encountered:
feat: try to canonicalize git-URLs (#1120)
0df6b74
Changed: `Factories.FromNodePackageJson.ExternalReferenceFactory.makeVcs()` tries to canonicalize git-URLs fixes #1119 --------- Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
jkowalleck
Successfully merging a pull request may close this issue.
https://github.com/CycloneDX/cyclonedx-node-npm/releases/edit/v1.19.2 introduced a fix
this was a quick fix to a larger problem: NPM manifest's
repository
is not guaranteed to be a URL.see https://docs.npmjs.com/cli/v10/configuring-npm/package-json#repository
so valid values could be like
git@gitlab.example.com:user/project.git
.the shortcuts with alternative protocols (
github:
,gitlab:
, etc) are out of scope, they are expected to be normalized before processing.The text was updated successfully, but these errors were encountered: