ci: generate provenance statement on release to increase security#159
Open
tnkuehne wants to merge 1 commit intosvecosystem:mainfrom
Open
ci: generate provenance statement on release to increase security#159tnkuehne wants to merge 1 commit intosvecosystem:mainfrom
tnkuehne wants to merge 1 commit intosvecosystem:mainfrom
Conversation
|
Contributor
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Following recent hacks on npm packages, it would be greatly appreciated if you could increase the trust level of the npm packages.
I added generation of provenance statements as outlined in this guide from npm: docs.npmjs.com/generating-provenance-statements
If you want to further increase the security after merging this, you could migrate this repo to trusted publishing