44 ms·

This was resolved in about an hour, looking at the issue linked. All things considered, that's great turn-around time for a fix.

• lsadam0 8y ago
  I mean sure, the turn-around time is great...but how did this pass review in the first place? This should never happen in a reasonably managed project.
  • andrew_ 8y ago
    It wasn't up for review. It was published out of band, and outside of the ESLint pipeline using likely stolen credentials. That's how that stuff sneaks in.
    • lsadam0 8y ago
      Ah, thanks for the clarification. At first I thought this made it through the actual release process.
• mrob 8y ago
  It's not completely resolved until everybody who was potentially compromised audits everything their credentials gave them control over and changes the credentials.
  • andrew_ 8y ago
    Is a bug not fully resolved until every machine on the planet running that software has upgraded to a version in which the bug doesn't exist? That'd be quite a silly assertion imho.