chore: Enforce Node supply chain protections#18
Open
quant-ranger[bot] wants to merge 1 commit into
Open
Conversation
quant-ranger
Bot
requested review from
Oliver Borchert (borchero) and
Daniel Elsner (delsner)
as code owners
July 13, 2026 17:15
Oliver Borchert (borchero)
approved these changes
Jul 13, 2026
Daniel Elsner (delsner)
approved these changes
Jul 14, 2026
X-Quant-Ranger: node-dependency-cooldown
quant-ranger
Bot
force-pushed
the
node-dependency-cooldown-fixes
branch
from
July 20, 2026 17:01
aef7cdc to
be31772
Compare
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.
This PR configures minimum dependency release ages for bun, pnpm and npm, and blocks exotic subdependencies in pnpm.
These settings delay installing newly published package versions that may have been compromised in a supply chain attack.
Exotic subdependencies can hide malicious code, so pnpm blocks them entirely.
Existing release-age exclusions are preserved, and any deployment-configured exemptions are added.
If you run into any problems, feel free to ping Jakob Klaushofer (@JakobKlaushoferQC) or Yannik Tausch (@ytausch).