Recordsnpmshebang-commandfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×2
<path>:<n> · const closeError = new Error(<str>) · ^ · Error: command failed
Evidence quality: complete · npm · unclassified-diagnostic · outer npm test · gap stage-unknown · First recorded: 2026-10-18 · Last seen: 2026-10-18
sha256:536db39a2e08…
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.
- 2.0.0 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-10-18 → 2026-10-18
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: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- shebang-command 2.0.0: shebangCommand 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. HOWshebangCommandnode 22.23.2 MIT-0 · 2026-08-26
- shebang-command 2.0.0 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-08-26