chore: enforce 3-day minimum release age for dependencies (supply-chain hardening)#4679
Open
vikyw89 wants to merge 1 commit into
Open
chore: enforce 3-day minimum release age for dependencies (supply-chain hardening)#4679vikyw89 wants to merge 1 commit into
vikyw89 wants to merge 1 commit into
Conversation
Supply-chain hardening. pnpm 10.16+ native minimumReleaseAge refuses to resolve any dependency version published less than 3 days ago (4320 min), so newly-published malicious versions get caught/yanked before we install. Workspace-wide, so it covers root, apps/* and packages/server. Only gates new resolutions; versions already pinned in the lockfile are unaffected. Closes Dokploy#4678 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dosubot
Bot
added
the
size:XS
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.
What
Adds
minimumReleaseAge: 4320topnpm-workspace.yaml— pnpm refuses to resolve any dependency version published less than 3 days ago.Why
Newly published npm versions are the highest-risk window for supply-chain attacks. Most malicious releases are detected and yanked within a day or two; a 3-day cooldown means a compromised version gets caught before it lands in CI or dev machines.
Notes
minimumReleaseAge(10.16+); repo is on pnpm 10.22, so no new dependency.apps/*, andpackages/server.pnpm-lock.yamlare unaffected, so installs from the committed lockfile keep working.minimumReleaseAgeExcludecan allowlist specific packages.Closes #4678
🤖 Generated with Claude Code