Recordsnpmjs-yaml4.3.1
Change the conditions
Current conditions
js-yaml @4.3.1windows 11 · x64 · node (version not recorded) · npm · node
package-level total, not an API
0 of 3 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 0 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 3
- Last recorded
- 2026-08-16
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| argparse | 2.0.1 | contract passed | 4 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.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.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×14 3.15.1 → 4.1.0 → 4.3.1 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 6 · First recorded: 2026-08-16 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×2 4.3.0 → 4.3.1 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-21Diagnostic re-verification candidate