Recordsnpmdetect-libcfailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×6
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-29 · Last seen: 2026-09-13
sha256:c12549970456…
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 2.1.2 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×5 2026-08-29 → 2026-08-31
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-09-13 → 2026-09-13
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- detect-libc 2.1.2: method 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. HOWdetect-libc.methodnode 22.23.2 MIT-0 · 2026-09-05
- detect-libc 2.1.2: GLIBC, MUSL, family 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. HOWdetect-libc.GLIBCdetect-libc.MUSLdetect-libc.familydetect-libc.familySyncdetect-libc.isNonGlibcLinuxdetect-libc.isNonGlibcLinuxSyncdetect-libc.versiondetect-libc.versionSyncnode 22.23.2 MIT-0 · 2026-08-27
- detect-libc 2.1.2: Prevent silent native addon resolution errors by accounting for detect-libc ignoring process.env overrides, returning null on non-Linux, and relying on multi-tier host probes 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. HOWfamilyfamilySyncisNonGlibcLinuxisNonGlibcLinuxSyncversionversionSyncGLIBCMUSLnode MIT-0 · 2026-08-16