Skip to content

chore(security): npm supply-chain cooldown — pin deps + .npmrc release-age#23

Closed
decentraliser wants to merge 2 commits into
EmblemCompany:mainfrom
decentraliser:chore/npm-supply-chain-cooldown
Closed

chore(security): npm supply-chain cooldown — pin deps + .npmrc release-age#23
decentraliser wants to merge 2 commits into
EmblemCompany:mainfrom
decentraliser:chore/npm-supply-chain-cooldown

Conversation

@decentraliser
Copy link
Copy Markdown
Contributor

Summary

Hardening the emblemai CLI (published @emblemvault/agentwallet) against the Shai-Hulud / TanStack npm+PyPI supply-chain wave (2026-05-12/13). PR from the working fork.

  • .npmrc: minimum-release-age=10080 (7-day cooldown) + save-exact=true
  • pin all 13 third-party direct deps to exact currently-resolved versions; kept @emblemvault/* deps (auth-sdk) as ^ ranges
  • regenerate package-lock.json (synced)

Recommended follow-ups (not in this PR)

  • npm publish --provenance so users who npm i -g can verify the tarball's build origin.
  • npm 2FA on the publish token.

Caveats

  • npm CLI doesn't enforce a rolling release-age cooldown the way pnpm/bun do — committed lockfile + npm ci + npm audit before publish is the real protection.
  • npm audit: 5 pre-existing transitive advisories (2 high) — not addressed here.

Test plan

  • CI green; npm ci && npm run typecheck && npm test

…e-age

Hardening against the Shai-Hulud / TanStack npm+PyPI supply-chain wave.

- add .npmrc: minimum-release-age=10080 (7d cooldown) + save-exact
- pin all 13 third-party direct deps to exact resolved versions; kept @emblemvault/*
  deps as ranges
- regenerate package-lock.json (synced)
- npm audit: 5 pre-existing transitive advisories (2 high) — left for a separate pass

L3-37 Claude
@decentraliser
Copy link
Copy Markdown
Contributor Author

Superseded by #21 — commits cherry-picked there (55c861a + 68b1e97). Closing.

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