Recordsnpmexpress5.2.1
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 3✓ · PROJECT_TEST 3✓ — Usage: USED 3✓ — Verified: CONTRACT 12✓
|
HIGH | 6 +3 | 12 | 100% | 1 · 3✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 1✓
|
LOW | 2 +1 | 1 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22.16 · JS · pnpm · windows
Observations: PROJECT_COMPILE 5✓ · PROJECT_PROCESS 1✓ · PROJECT_TEST 5✓ 3✕ — Usage: USED 72✓
|
LOW | 14 +72 | 0 | 79% | 1 | 2026-08-23 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 4✓ 1✕
|
LOW | 5 | 0 | 80% | 1 | 2026-08-21 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 6✓
|
LOW | 6 | 0 | 100% | 1 | 2026-08-21 |
| node 24.13 · TS · npm · windows
Usage: USED 1✓
|
LOW | 0 +1 | 0 | — | 1 | 2026-08-13 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 1✓ 2✕ — Usage: USED 1✓
|
LOW | 3 +1 | 0 | 33% | 1 | 2026-08-14 |
| node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 2✓ · PROJECT_TEST 4✓ 1✕ · PROJECT_TYPECHECK 2✓ 1✕ — Usage: USED 39✓
|
LOW | 10 +39 | 0 | 80% | 1 | 2026-08-21 |
| node 24.13 · JS · pnpm · windows
Observations: PROJECT_COMPILE 8✓ · PROJECT_TEST 14✓ 2✕ — Usage: USED 25✓ — Verified: UNKNOWN 0✓ 2✕
|
LOW | 24 +25 | 2 | 85% | 1 | 2026-08-29 |
Recent failure clusters
-
observed PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×13 5.1.0 → 5.2.1 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-13 · Last seen: 2026-08-21Diagnostic re-verification candidate
-
observed PROJECT_TEST Evidence gap ×5 5.2.1 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×1 5.2.1 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 PROJECT_TEST exit 1 ELIFECYCLE ×1 5.2.1 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:7711694d48fa…ELIFECYCLE Test failed. See above for more details.javascript/test-runner · test-runner-diagnostic · outer pnpm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed UNKNOWN exit 1 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Evidence gap ×1 5.2.1 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:0903ef5db350…(node:<n>) ExperimentalWarning: SQLite is an experimental feature and might change at any time …pnpm · unclassified-diagnostic · outer pnpm · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Evidence gap ×1 5.2.1 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:d53178e9c23b…<str> is not recognized as an internal or external command, · operable program or batch file. · undefined · <path>pnpm · unclassified-diagnostic · outer pnpm · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
Symbols
- Router 2 shared ×2 2 of 2 runs passed
- req.accepts 1 2 of 2 runs passed
- req.acceptsEncodings 1 2 of 2 runs passed
- res.cookie 2
- res.download 1
- express 3 3 of 3 runs passed
- req.get 2 2 of 2 runs passed
- req.is 1 2 of 2 runs passed
- res.json 3
- req.params 1
- req.query 2
- req.range 1
- res.redirect 1
- app.router 1 2 of 2 runs passed
- res.send 2
- res.sendFile 1
- res.sendStatus 1
- app.use 2 3 of 3 runs passed
Published samples
- express 5.2.1 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-20