Recordsnpmjs-yamlfailure issue
Failure signature
PROJECT_PROCESS Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-26
js-yaml.CORE_SCHEMA js-yaml.DEFAULT_SCHEMA js-yaml.FAILSAFE_SCHEMA js-yaml.JSON_SCHEMA js-yaml.Schema js-yaml.SchemaDefinition js-yaml.Type js-yaml.YAMLException js-yaml.dump js-yaml.load js-yaml.loadAll
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.3.1 PASS 59 passing observations
- 4.3.0 PASS 7 passing observations
- 4.1.1 PASS 11 passing observations
- 4.1.0 FAIL
- 3.15.2 PASS 24 passing observations
- 3.15.1 PASS 29 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-26 → 2026-08-26
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 3.15.2 → first failing release 4.1.0
What differs across the boundary
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 4.1.0 → first passing release 4.1.1
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 | 4.3.1 | 4.3.0 | 4.1.1 | 4.1.0 | 3.15.2 | 3.15.1 |
|---|---|---|---|---|---|---|
| argparse | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 | 1.0.10 | 1.0.10 |
| esprima | — | — | — | — | 4.0.1 | 4.0.1 |
Moved: 1 · unchanged at every release: 1
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- js-yaml 4.1.0: loadAll 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. HOWjs-yaml.loadAllnode 22.23.2 MIT-0 · 2026-08-28
- js-yaml 4.1.0: load 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. HOWjs-yaml.loadnode 22.23.2 MIT-0 · 2026-08-28
- js-yaml 4.1.0: dump 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. HOWjs-yaml.dump MIT-0 · 2026-08-28