Skip to content

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

Merged
royosherove merged 1 commit into
mainfrom
security/npm-quarantine
May 12, 2026
Merged

security: add supply-chain quarantine (.npmrc min-release-age=7)#8
royosherove merged 1 commit into
mainfrom
security/npm-quarantine

Conversation

@royosherove
Copy link
Copy Markdown
Member

Adds org-wide min-release-age=7 quarantine after the 2026-05-12 Mini Shai-Hulud wave. We were not compromised. Closes the policy gap.

@royosherove royosherove merged commit 0970c1c into main May 12, 2026
@royosherove royosherove deleted the security/npm-quarantine branch May 12, 2026 19:37
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6b6d12865e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .npmrc
# 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
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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant