garbled package metadata delivered to old npm clients

Incident Report for npm

Resolved

We believe all package data with incorrect caching headers has been replaced in cache.

Posted Apr 07, 2016 - 03:36 UTC

Monitoring

A change made to the npm registry on 2016-04-04 unexpectedly triggered build failures for some users of older versions of the npm CLI (including those packaged by LTS OS distributions). A fix that the npm operational team rolled out was incomplete, but has since been correctly deployed across our infrastructure. Please see https://github.com/npm/npm/issues/12196#issuecomment-206525005 for more details.

Posted Apr 06, 2016 - 20:15 UTC