Recordsnpmbare-path
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| bare-path | bare-path.basename | bare-path.delimiter | bare-path.dirname | bare-path.extname | bare-path.isAbsolute | bare-path.join | bare-path.sep | |
|---|---|---|---|---|---|---|---|---|
| glibc | 70%23 | 69%16 | 69%16 | 69%16 | 69%16 | 69%16 | 69%16 | 68%19 |
Showing the environments with the most evidence.
How to read the grid
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 ◆ mark says one thing only: this network ran its own contract in THIS environment and it came back clean. Whether code exists for the release and API is a separate mark and a separate fact, because a sample does not stop existing when you switch the OS filter.
- there is sample code for this release and API, whatever the environment
- we ran our own contract in this environment and it came back clean
- our sample failed here
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
Code availability is a fact about this release and this API. It does not change with OS, runtime or package manager — whether it was verified HERE is the separate mark beside it.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.