Recordsnpmnpm-package-arg12.0.2Result
Change the conditions
Current conditions
Result @12.0.2debian glibc · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
12.0.2
linux · node@22.23 · executionContext=node · moduleSystem=esm
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| hosted-git-info | 8.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 44 project-days |
| proc-log | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 44 project-days |
| semver | 7.7.4 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| semver | 7.8.5 | CANDIDATE Correlated change; unproven combination | contract passed | 41 project-days |
| validate-npm-package-name | 6.0.2 | 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 | 13.0.2 | 12.0.2 |
|---|---|---|
| hosted-git-info | 9.0.2 | 8.1.0 |
| proc-log | 6.1.0 | 5.0.0 |
| semver | 7.7.3 | 7.7.4 |
| validate-npm-package-name | 7.0.2 | 6.0.2 |
Moved: 4 · unchanged at every release: 0
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 ×2 12.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:536db39a2e08…<path>:<n> · const closeError = new Error(<str>) · ^ · Error: command failednpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 12.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:2c4eb57fcc76…AssertionError [ERR_ASSERTION]: Missing expected exception. · at <url> · at ModuleJob.run (node:internal/modules/esm/module_job:<n>:<n>) …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 12.0.2 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:8c3539be02dd…AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: · + actual - expected · Comparison { · + message: <str>,javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18