-
Notifications
You must be signed in to change notification settings - Fork 75
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
[BUG] fix openvex report oci id #667
Comments
@sozercan looks a good first issue to work on this repo but will need more info ? |
@sozercan, can image be an image digest if yes then we can modify the patchWithContext( ) there. Line 78 in aec1c59
|
@prakrit55 Didn't see any comment , that's fine , will also update if found any helpful info , also looking to collaborate on this one or flying solo? |
@shubhamsugara22, you can work into it, I will go find another one 😄 |
I'd love to take a shot at this bug if everyone is okay with it! |
Version of copa
No response
Expected Behavior
it should be:
https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#oci
However, I am not sure if we can do this since image is not at the registry at this time so sha256 will not be accurate. tag might be more suitable?
Actual Behavior
vex statement output has
https://project-copacetic.github.io/copacetic/website/output
Steps To Reproduce
No response
Are you willing to submit PRs to contribute to this bug fix?
The text was updated successfully, but these errors were encountered: