WhatBrokeToday
GTA 6FAQ

npm vs Sentry: reliability

In the last 60 days, npm had 14 incidents (median fix 1 min) and Sentry had 13 incidents (median fix 1 min). Sentry broke less often.

Side by side, last 60 days

npm and Sentry reliability over the last 60 days
MeasurenpmSentry
Incidents (60 days)1413
Critical or high89
Median time to fix1 min1 min
Longest incident1 h53 min
Never on its status page80
Status page delay (median)1 min1 min
30-day hazard rating8.8 / 107.6 / 10

npm's worst incidents

npm's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
Multiple NPM Packages Contain Malicious Code

Cause: Publication of malicious package versions containing malware.

criticalongoingnot yet
Vant NPM Package Malicious Versions Published

Cause: Malicious code and install hooks ('postinstall': 'node lib/utils/support.js') were added to multiple versions of the vant package.

criticalongoingnot yet
Mongoose sanitizeFilter Vulnerability in countDocuments

Cause: The sanitizeFilter protection mechanism was not applied during countDocuments() queries in affected versions.

criticalongoingnot yet
bitcoinjs-lib Undetected Merkle Node Duplication Vulnerability

Cause: `fastMerkleRoot` pads an odd level by hashing the last node with itself without reporting it, and `checkTxRoots` fails to look for repeated transactions.

criticalongoingnot yet
node-opcua Namespace-Level RBAC Fail-Open Vulnerability

Cause: Namespace-level RBAC fail-open via unbound DefaultRolePermissions allowing anonymous write and call bypasses.

criticalongoingnot yet
Full npm outage history

Sentry's worst incidents

Sentry's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
Sentry.io dashboard and API is downcritical1 minfirst
Sentry dashboard is downcritical1 minfirst
Sentry.io not loading in US regioncritical1 minfirst
Sentry is downcritical1 minfirst
Sentry dashboard downcritical1 minfirst
Full Sentry outage history