Harden the pinned npm release CLI - #42
Merged
Merged
Conversation
Derive the staging CLI from npm 11.19.0 with integrity-pinned security updates, require a clean audit, and checksum the exact artifact used for publishing. Add a path-scoped CI workflow that exercises the same preparation pipeline without publishing. Closes #41
|
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
Closes #41.
Testing
bun run format:writebun run check-typesbun run lint(passes with four pre-existing CSS specificity warnings)bun run testactionlint .github/workflows/ci.yml .github/workflows/publish-npm.yml .github/workflows/verify-pinned-npm.ymlnpm stage --helpverificationbun run release:audit --workspace apps/cli --include @biomejs/biome --include esbuild --include turbobun --filter artiflow buildGreptile Summary
The PR replaces temporary npm audit exceptions with an integrity-pinned hardening pipeline for npm 11.19.0 and uses the resulting audited artifact during release staging.
Confidence Score: 5/5
The PR appears safe to merge, with no concrete changed-code failure identified.
The hardening, audit, checksum, artifact transfer, extraction, and staging paths are internally consistent, and the investigation found no reachable blocking or non-blocking defect.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Pack official npm 11.19.0] --> B[Extract npm archive] B --> C[Replace four bundled dependencies] C --> D[Validate versions, integrity, and dependency contracts] D --> E[Generate shrinkwrap] E --> F[Run production audit] F --> G[Create hardened archive] G --> H[Checksum official and hardened archives] H --> I[Upload release artifacts] I --> J[Verify checksums in staging job] J --> K[Extract hardened npm] K --> L[Run npm stage publish]Reviews (1): Last reviewed commit: "fix(release): harden pinned npm CLI" | Re-trigger Greptile