Recordsnpmsmart-buffer4.2.0smart-buffer.SmartBuffer
OS × runtime at a glance
2○ 12026-09-07
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.
Published samples
- smart-buffer 4.2.0: SmartBuffer 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. HOWsmart-buffer.SmartBuffer MIT-0 · 2026-08-23
Compatibility matrix
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
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-23 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 1✓
|
LOW | 1 | 1 | 100% | 1 · 1✓ | 2026-09-07 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-23 |
snapshot · 2026-09-15
Failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×15 4.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 4.2.0 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-18 · Last seen: 2026-08-26Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×5 4.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×4 4.2.0 executionContext=node · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed UNKNOWN exit 2 Evidence gap ×4 4.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:fddf8ea09045…Using CPython 3.12.3 interpreter at: <path> · Creating virtual environment at: .venv · error: Failed to create virtual environment …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×4 4.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:72ba2d1e946f…<path>: No module named pippython3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 4.2.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 4.2.0 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:c113861ea657…<str> is not recognized as an internal or external command, · operable program or batch file. · > wslpad@1.1.0 test · > vitest runnpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed PROJECT_TEST ENOENT Evidence gap ×2 4.2.0 executionContext=node · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-18 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×2 4.2.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:536db39a2e08…<path>:<n> · const closeError = new Error(<str>) · ^ · Error: command failednpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×1 4.2.0 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-21 · Last seen: 2026-08-21
-
observed UNKNOWN exit 1 ECONNREFUSED Evidence gap ×1 4.2.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:33b25a11df76…node:events:<n> · throw er; <path> Unhandled <str> event · ^ · Error: connect ECONNREFUSED <ip>:<port>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
Showing the 12 most-reported of 49 recorded failure clusters. The rest are single reports.