Skip to content

Increase min release age to 48h #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yosriady merged 1 commit into from
May 12, 2026
Merged

Increase min release age to 48h #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
audit=true
block-exotic-subdeps=true
minimum-release-age=25h
minimum-release-age=48h
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Increasing the minimum-release-age to 48 hours is a strong security measure against dependency hijacking, but it may significantly impact development velocity. This setting blocks the installation of any package version released within the last 48 hours, which includes critical bug fixes or security patches from upstream dependencies. Consider if this two-day delay is acceptable for your workflow, or if a 24-hour window (e.g., 24h) would provide a better balance between security and operational agility.