Records/npm/parse-conflict-json

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

• – no sample at this coordinate yet
• there is a sample here, and nothing of ours has run it at this coordinate yet
• there is a sample here, and our run of it at this coordinate came back clean
• there is a sample here, and our run of it at this coordinate failed
• there is a sample here, and this coordinate records both a passing and a failing run of it
• — nothing recorded — unknown, never "works" and never "broken"
• › there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.