Skip to content

security: add supply-chain quarantine (.npmrc min-release-age=7) #8

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
royosherove merged 1 commit into from
May 12, 2026
Merged

security: add supply-chain quarantine (.npmrc min-release-age=7) #8

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
4 changes: 4 additions & 0 deletions .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# Supply-chain quarantine: refuse to install any npm package published < 7 days ago.
# Organization-wide policy; critical after 2026-05-12 Mini Shai-Hulud wave
# (@mistralai/mistralai 2.2.2-2.2.4, 169 packages total).
min-release-age=7

@chatgpt-codex-connector chatgpt-codex-connector Bot May 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Replace unsupported npm config key

I checked this change in /workspace/pi-hard-no with npm 11.4.2, and npm reports Unknown project config "min-release-age" when reading this setting (e.g., via npm config get min-release-age), which means this line is not enforced during installs. As written, the commit claims to add a supply-chain quarantine but leaves the policy gap open because package installs still proceed without age gating; please switch to a quarantine control that npm actually supports (or enforce it in a tool that supports this key).

Useful? React with 👍 / 👎.

Loading