Recordsnpmmake-fetch-happenfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
> wslpad@1.0.2 test:e2e · > playwright test test/e2e/dashboard.spec.ts · Running 15 tests using 1 worker …
Evidence quality: complete · npm · unclassified-diagnostic · outer npm run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:6d81a9d59cd0…
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=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15
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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 15.0.6 | 15.0.3 | 14.0.3 | 10.2.1 |
|---|---|---|---|---|
| @npmcli/agent | 4.0.2 | 4.0.0 | 3.0.0 | — |
| cacache | 20.0.4 | 20.0.3 | 19.0.1 | 16.1.3 |
| minipass | 7.1.3 | 7.1.2 | 7.1.3 | 3.3.6 |
| minipass-fetch | 5.0.2 | 5.0.0 | 4.0.1 | 2.1.2 |
| minipass-flush | 1.0.6 | 1.0.5 | 1.0.5 | 1.0.7 |
| negotiator | 1.0.0 | 1.0.0 | 1.0.0 | 0.6.4 |
| proc-log | 6.1.0 | 6.1.0 | 5.0.0 | — |
| ssri | 13.0.1 | 13.0.0 | 12.0.0 | 9.0.1 |
| @gar/promise-retry | 1.0.3 | — | — | — |
| @npmcli/redact | 4.0.0 | — | — | — |
| agentkeepalive | — | — | — | 4.6.0 |
| http-cache-semantics | 4.2.0 | 4.2.0 | 4.2.0 | 4.2.0 |
| http-proxy-agent | — | — | — | 5.0.0 |
| https-proxy-agent | — | — | — | 5.0.1 |
| is-lambda | — | — | — | 1.0.1 |
| lru-cache | — | — | — | 7.18.3 |
| minipass-collect | — | — | — | 1.0.2 |
| minipass-pipeline | 1.2.4 | 1.2.4 | 1.2.4 | 1.2.4 |
| promise-retry | — | 2.0.1 | 2.0.1 | 2.0.1 |
| socks-proxy-agent | — | — | — | 7.0.0 |
Moved: 8 · unchanged at every release: 12
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
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.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.