Recordsnpmadm-zip0.6.1
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
12026-09-16
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 glibc · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
|
LOW | 4 +2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓ · PROJECT_TEST 1✓
|
LOW | 2 | 0 | 100% | 1 | 2026-09-16 |
| node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 6✓ · PROJECT_PROCESS 3✓ — Usage: USED 36✓ — Verified: UNKNOWN 0✓ 7✕
|
ELEVATED FAILURE | 9 +36 | 7 | 56% | 1 | 2026-09-16 |
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:2cb056298ab4…SELFTEST FAIL bounded-time · SELFTEST FAIL config-generation-keyframe-cut · dxgi replay ring self-test: FAIL · node:internal/errors:<n>npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:819cb89d1c79…<url> · throw new Error( · ^ · Error: DXGI replay native self-test markers changed or were incomplete:npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:86e62e0f88c9…SELFTEST FAIL retention-export-window-anchors-to-latest-encoded-sample · dxgi replay ring self-test: FAIL · node:internal/errors:<n> …npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:92afbc39da22…<url> · throw new Error( · ^ · Error: dxgi-replay-ring.exe compile failed (2): dxgi-replay-ring.cppnpm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:a0a8ceaaf237…> capturepack@0.5.1 check:site · > node <path> · Landing translations · PASS en: 42 rendered stringsnpm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:aa33afc48c64…...ppData\Local\Temp\capturepack-dxgi-runtime-check-Rt8eb9\check.cjs 95.9kb · Done in 11ms · dxgi replay integration check: 1 failed …npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 EPERM Evidence gap ×1 0.6.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 adm-zip.IZipEntry sha256:b40ca5d413e3…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · [Error: EPERM: operation not permitted, unlink <str>] {npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16Diagnostic re-verification candidate
Symbols
- adm-zip.IZipEntry 0 of 7 runs passed
Published samples
- adm-zip 0.6.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. HOWnode 22.23.2 MIT-0 · 2026-09-16