Verify npm dependency signatures before builds - #402
Draft
zaniebot wants to merge 1 commit into
Draft
Conversation
This was referenced Aug 18, 2026
eifinger
pushed a commit
that referenced
this pull request
Aug 20, 2026
`devEngines` is ignored by npm releases such as `10.8.2`, so those clients can install dependencies without applying the seven-day `min-release-age` setting added in #401. Declare the same minimum in `engines.npm` and enable `engine-strict` to make that legacy installer requirement fatal. Keep `devEngines` for its earlier checks on newer npm versions, and pin the build and checksum workflows to Node.js `24.19.0` so their bundled `npm` supports the policy. Related: astral-sh/setup-uv#1026 and astral-sh/ruff#27844 enforce the same legacy-aware `npm` version floor. #400 covers Dependabot's update cooldown, and #402 separately verifies registry signatures and available provenance. --------- Co-authored-by: zaniebot <242828183+zaniebot@users.noreply.github.com>
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.
CI installs the locked npm dependency tree without running lifecycle scripts, but it does not verify registry signatures or available provenance attestations. Run
npm audit signaturesafter installation in both the test and checksum-update workflows, beforenpm run allexecutes dependency tooling. The check follows npm's registry-signature support and verifies attestations when present; it does not require every dependency to publish provenance.Related: astral-sh/setup-uv#1027 adds the same signature and provenance verification. #401 separately hardens
npminstall defaults.