Recordsnpmminimistfailure issue
Failure signature
UNKNOWN signal KILLED Evidence gap ×1
Evidence quality: partial · npm · unclassified-diagnostic · outer npm install · gap diagnostic-missing · First recorded: 2026-09-04 · Last seen: 2026-09-04
sha256:08397c21dc67…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-04 → 2026-09-04
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 UNKNOWN.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- minimist 1.2.8: parse CLI arguments with string, boolean options, aliases and defaults using minimist 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. HOWminimist MIT-0 · 2026-08-28