Recordsnpmscheduler0.25.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
Showing the environments with the most evidence.
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.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 12✓
|
LOW | 4 +2 | 12 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 2✓
|
LOW | 2 +1 | 2 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 2✓ 1✕
|
LOW | 3 | 0 | 67% | 2 | 2026-08-21 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-16 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 2✓
|
LOW | 2 | 0 | 100% | 1 | 2026-08-16 |
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 0.23.2 → 0.25.0 → 0.27.0 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-18 · Last seen: 2026-08-29Diagnostic re-verification candidate
Symbols
- scheduler.unstable_IdlePriority 1 1 of 1 runs passed
- scheduler.unstable_ImmediatePriority 1 1 of 1 runs passed
- scheduler.unstable_LowPriority 1 1 of 1 runs passed
- scheduler.unstable_NormalPriority 1 1 of 1 runs passed
- scheduler.unstable_UserBlockingPriority 1 1 of 1 runs passed
- scheduler.unstable_cancelCallback 1 1 of 1 runs passed
- scheduler.unstable_getCurrentPriorityLevel 1 1 of 1 runs passed
- scheduler.unstable_getFirstCallbackNode 1 1 of 1 runs passed
- scheduler.unstable_now 1 1 of 1 runs passed
- scheduler.unstable_runWithPriority 1 1 of 1 runs passed
- scheduler.unstable_scheduleCallback 1
- scheduler.unstable_shouldYield 1
- scheduler.unstable_wrapCallback 1
Published samples
- scheduler 0.25.0 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-21