add note about nuget checksums #277
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stevespringett
added
the
PURL type definition
|
Thank you for this PR @matt-phylum . When you have the chance, could you please merge the latest master into this branch? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds clarification around NuGet package checksum qualifiers.
Should there also be a
nuget_lock_sha512qualifier or similar for holding the package hash? It could be useful for cases where somebody is trying to generate an SBOM from apackages.lock.jsonfile. NuGet packages are not namespaced by their source repository and the source repository information is not included in thepackages.lock.jsonfile. The package hash is the only disambiguating information in that case if there are multiple packages with the same name and version.