Fix pinned npm release audit - #39
Merged
Merged
Conversation
Keep the npm CLI audit fail-closed while temporarily accepting only the known advisory, package, and bundled-version tuples for npm 11.18.0. Expire the exceptions on 2026-08-24 and reject all policy drift.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Summary
Testing
bun run format:writebun run check-typesbun run lint(passes with four pre-existing CSS specificity warnings)bun run testbun run release:audit --workspace apps/cli --include @biomejs/biome --include esbuild --include turbobun --filter artiflow buildactionlint .github/workflows/publish-npm.ymlGreptile Summary
The PR replaces the pinned npm release’s binary audit gate with a narrowly scoped policy for npm 11.18.0.
Confidence Score: 5/5
The PR appears safe to merge because no concrete blocking or independently actionable non-blocking defect remains.
The workflow audits the intended extracted npm tree using the pinned audit engine, and the new validator fails closed on npm-version drift, unexpected findings, malformed data, unresolved installed versions, and expired exceptions.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Download npm 11.18.0 tarball] --> B[Extract npm package] B --> C[Generate shrinkwrap] C --> D[Run npm audit as JSON] D --> E[Resolve installed package versions] E --> F{Exact npm version?} F -- No --> X[Fail release] F -- Yes --> G{All moderate+ findings match allowed advisory/package/version tuples?} G -- No --> X G -- Yes --> H{Accepted exceptions expired?} H -- Yes --> X H -- No --> I[Record checksum] I --> J[Verify checksum in stage job] J --> K[Stage package publish]Reviews (1): Last reviewed commit: "fix(release): narrowly allow pinned npm ..." | Re-trigger Greptile