npm: Public replication endpoint taken offline due to security incident
Timeline of updates
- resolved
Public skimdb is now repaired and back up.
From npm’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.npmjs.org (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by npm, started 2015-07-02 14:32 UTC, resolved after 42 min, 1 update(s).
- Title
- Public replication endpoint taken offline due to security incident
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/6r2jr0dd9kd5
npm profileRecent npm incidentsAll outages on July 2, 2015npm in July 2015MarkdownJSON