purl: add non-nil Source field to all PURL parse functions #1744
Conversation
This file contains hidden or 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
crozzy
previously approved these changes
Jan 26, 2026
BradLugo
force-pushed
the
blugo/purl-fix
branch
from
14f4101 to
9673835
Compare
crozzy
approved these changes
Jan 26, 2026
The matching logic requires that a claircore.Package contain a non-nil Source field value. Signed-off-by: Brad Lugo <[email protected]>
BradLugo
force-pushed
the
blugo/purl-fix
branch
from
9673835 to
bcc2f4a
Compare
Contributor
|
/fast-forward |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.