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
Hi,
I'm writing a script to generate SBOM content for my JSR deps, and I've noticed that the latest versions of a couple of std packages are missing the provenance link to Rekor: https://jsr.io/@std/collections/1.0.8 and https://jsr.io/@std/streams/1.0.7
The previous versions (https://jsr.io/@std/collections/1.0.7 and https://jsr.io/@std/streams/1.0.6) do have this, as well as the latest versions of the other @std packages I checked.
@std
I don't know if it represents a security problem, but it's surprising (and causing some difficulties for my SBOM generation!)
Thanks, Adam
The text was updated successfully, but these errors were encountered:
[email protected] also didn't get the provenance https://jsr.io/@std/[email protected]
Sorry, something went wrong.
[email protected] also doesn't have provenance https://jsr.io/@std/[email protected]
Note: This happens when the publishing failed in the middle of the process.
This is currently worked on at denoland/deno#26829
No branches or pull requests
Hi,
I'm writing a script to generate SBOM content for my JSR deps, and I've noticed that the latest versions of a couple of std packages are missing the provenance link to Rekor: https://jsr.io/@std/collections/1.0.8 and https://jsr.io/@std/streams/1.0.7
The previous versions (https://jsr.io/@std/collections/1.0.7 and https://jsr.io/@std/streams/1.0.6) do have this, as well as the latest versions of the other
@std
packages I checked.I don't know if it represents a security problem, but it's surprising (and causing some difficulties for my SBOM generation!)
Thanks,
Adam
The text was updated successfully, but these errors were encountered: