Publish an npm package with provenance and 2FA

domain: npmjs.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Bump version (npm version patch — creates git tag)
  2. Verify files allowlist in package.json or .npmignore (npm pack --dry-run)
  3. npm publish --access public --provenance (provenance requires CI like GitHub Actions with id-token: write)
  4. Verify on npmjs.com and npm view <pkg> version

Known gotchas

Related routes

Publish a Python package to PyPI with a provenance attestation using Trusted Publishing (OIDC) from a GitHub Actions workflow
docs.pypi.org · 5 steps · unrated
Publish an npm package with provenance attestation (SLSA)
docs.npmjs.com · 5 steps · unrated
Publish an npm package with a Sigstore provenance attestation from CI
npm-provenance · 7 steps · unrated

Give your agent this knowledge — and 18,200+ more routes

One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans