Recordsnpmfs-extrafailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×2
Contract test failed: AssertionError [ERR_ASSERTION]: DOWNLOAD_PROGRESS event should have fired · false !== true · at main (<path>:<n>:<n>) { …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-08-29 · Last seen: 2026-08-29
sha256:45fc70285a65…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 11.4.0 PASS 247 passing observations
- 11.3.1 PASS 231 passing observations
- 11.3.0 PASS 3 passing observations
- 10.1.0 FAIL
- 9.1.0 PASS 248 passing observations
- 8.1.0 PASS 247 passing observations
- 7.0.1 PASS 231 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-29 → 2026-08-29
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 9.1.0 → first failing release 10.1.0
What differs across the boundary
- at-least-node 1.0.0 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release 10.1.0 → first passing release 11.3.0
Both trees resolved every dependency to the same version. Nothing here moved.
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 | 11.4.0 | 11.3.1 | 11.3.0 | 10.1.0 | 9.1.0 | 8.1.0 | 7.0.1 |
|---|---|---|---|---|---|---|---|
| jsonfile | 6.2.1 | 6.2.1 | 6.2.1 | 6.2.1 | 6.2.1 | 4.0.0 | 4.0.0 |
| universalify | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 | 0.1.2 | 0.1.2 |
| at-least-node | — | — | — | — | 1.0.0 | — | — |
| graceful-fs | 4.2.11 | 4.2.11 | 4.2.11 | 4.2.11 | 4.2.11 | 4.2.11 | 4.2.11 |
Moved: 2 · unchanged at every release: 2
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
- No failure domain was inferred for this failure.
Published answers for the affected releases
- fs-extra 10.1.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-20
- fs-extra 10.1.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-20