Skip to content

security: add 7-day exclude-newer cooldown#258

Open
burnpiro wants to merge 1 commit into
mainfrom
security/cooldown-7d
Open

security: add 7-day exclude-newer cooldown#258
burnpiro wants to merge 1 commit into
mainfrom
security/cooldown-7d

Conversation

@burnpiro

Copy link
Copy Markdown

What

Adds exclude-newer = "7 days" to [tool.uv] so new PyPI uploads are filtered out until they've been on the index for ≥ 7 days.

zeroband has no first-party PrimeIntellect packages in its closure, so no [tool.uv.exclude-newer-package] exemptions are needed yet — the comment in pyproject.toml documents when to add one.

Why

Most malicious PyPI uploads (typosquatting, account takeovers, dependency confusion) are detected and yanked within hours-to-days. A short cooldown quarantines them at near-zero cost. Part 1 of 3 in a coordinated supply-chain hardening across PrimeIntellect repos.

Notes

  • uv.lock diff is large but mechanical: uv migrated the lockfile schema from revision = 2revision = 3. The semantic diff is just the new [options] block recording the cooldown. Zero packages removed; zero version regressions.
  • uv lock --check passes locally.
  • Benign deprecation warning on tool.uv.dev-dependencies (pre-existing; should migrate to dependency-groups.dev in a follow-up).

🤖 Generated with Claude Code

Refuse to resolve any PyPI dependency uploaded in the last 7 days
(`[tool.uv] exclude-newer = "7 days"`). Mitigates blast radius of
compromised dependencies (typosquatting, account takeovers, dependency
confusion).

Pins `required-version = ">=0.11.1"` so older uvs fail loudly instead
of silently parsing "7 days" as an RFC 3339 date and proceeding
*without* the cooldown — see uv#17908.

zeroband has no first-party PrimeIntellect packages in its dep closure,
so no `[tool.uv.exclude-newer-package]` exemptions are needed. Add the
table when that changes.

Lock regenerated: uv migrated the lockfile schema from revision 2 to
revision 3 (large mechanical churn — 0 packages removed, 0 versions
regressed). Schema migration is independent of the cooldown change.

Part 1 of 3 in a coordinated supply-chain hardening across PI repos.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@burnpiro burnpiro force-pushed the security/cooldown-7d branch from 4ce1599 to 79a388e Compare May 29, 2026 20:30
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