Recordsnpmjs-yaml4.3.2
Change the conditions
Current conditions
js-yaml @4.3.2windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
0 of 7 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 10 / 10
- Contract verifications
- 0 / 7
- Usage records
- 36
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.3.2
linux · node@22.23 · moduleSystem=cjs · executionContext=node
11 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| argparse | 2.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 42 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.2 | 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 | 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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×6 4.3.1 → 4.3.2 executionContext=node · moduleSystem=cjs sha256:bc4d7ddc5bcd…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>npm · unclassified-diagnostic · outer npm run, npm test · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-15Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×4 4.3.1 → 4.3.2 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-16Diagnostic re-verification candidate