feat: npm package configuration and binary installation script#2244
Draft
chinmaypant21 wants to merge 1 commit into
Draft
feat: npm package configuration and binary installation script#2244chinmaypant21 wants to merge 1 commit into
chinmaypant21 wants to merge 1 commit into
Conversation
…nd binary installation script
github-actions
Bot
added
🦺 github-action
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.
Related to the discussion in #1861.
It's only for reference, just a draft.
publish-npm.yml- ensures that the npm package stays in sync with our GitHub releases.package.json&install.js- We publish a tiny "wrapper" package to npm so Node.js/JavaScript developers can install Noir usingnpm install -g @owasp-noir/noirornpx @owasp-noir/noir -b .Security:
The
--provenanceflag in yml is a supply-chain security feature. It uses GitHub Actions secure identity token to cryptographically sign the published package. This is related to Trusted Publishing, and aligns with github's npm supply-chain security recommendations@hahwul @ksg97031
I'm looking forward to hear your thoughts and any suggestions for improving this approach.