Add npm-script-lens to Security Hardening 馃馃馃 - #154
Open
Booyaka101 wants to merge 1 commit into
Open
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
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.
Adds npm-script-lens to Security Hardening, alongside the existing
@lavamoat/allow-scriptsandare-scripts-enabledentries.npm 12, pnpm 10.26+, yarn Berry and bun have all made install scripts opt-in, which leaves maintainers looking at a list of package names asking which are safe to allow. This answers that with evidence rather than a name: it statically analyses the script source with acorn (following
node <file>targets,node -ebodies andnpm runrecursion), reads insidebinding.gypbecause gyp executes command expansions at configure time, and resolves the npm provenance attestation to its build identity so an upgrade that changes source repo or workflow shows up.Disclosure: I am the author, and this PR was prepared by an AI agent, opted into the agent process with 馃馃馃 per CONTRIBUTING.md.
Against the guidelines: searched for duplicates first (none), added to the end of its list, individual PR for this single suggestion, description starts with a capital and ends with a period, no trailing whitespace.