Minor impactResolvedDevOps

npm incident: Issue with package publish with provenance

npm reported this minor-impact incident on its official status page on Jun 12, 2025, 21:00 UTC. It was resolved after 1h 25m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Jun 12, 2025, 21:00 UTC
started
Jun 12, 2025, 22:25 UTC
resolved
1h 25m
duration
Minor
impact

Affected components

  • Package publishing

Timeline

updates from npm's status page ↗
  1. resolvedJun 12, 2025, 22:25 UTC

    This incident has been resolved.

  2. investigatingJun 12, 2025, 21:00 UTC

    We are seeing issues with package publish with provenance due to an outage of a key third party dependency.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in npm's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does npm have incidents?

npm reported 8 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 59m. See npm's uptime and incident history

← Previous: Issues with package install, package publish, and login. (Jun 12, 2025)Next: Incident with npm registry and website affecting logins and publishing (Aug 7, 2025) →
npm incident on Jun 12, 2025: Issue with package publish with provenance · APIStatus.watch