WhatBrokeToday
GTA 6FAQ

Grafana vs npm: reliability

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

Side by side, last 60 days

Grafana and npm reliability over the last 60 days
MeasureGrafananpm
Incidents (60 days)614
Critical or high18
Median time to fix58 min1 min
Longest incident9 h1 h
Never on its status page28
Status page delay (median)1 min1 min
30-day hazard rating4.0 / 108.8 / 10

Grafana's worst incidents

Full Grafana outage history

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