Recordsnpm@npmcli/installed-package-contents3.0.0
Change the conditions
Current conditions
@npmcli/installed-package-contents @3.0.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 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 failed (1)
- Project observations
- 26 / 28
- Contract verifications
- 0 / 1
- Usage records
- 31
- Independent reporting peers
- 1
- Last recorded
- 2026-10-21
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.0.0
linux · node@22.23 · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| npm-bundled | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 45 project-days |
| npm-normalize-package-bin | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 45 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.0.0 | 3.0.0 |
|---|---|---|
| npm-bundled | 5.0.0 | 4.0.0 |
| npm-normalize-package-bin | 5.0.0 | 4.0.0 |
Moved: 2 · 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 ERR_ASSERTION Evidence gap ×2 3.0.0 → 4.0.0 executionContext=node · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-09-14 · Last seen: 2026-10-20Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 3.0.0 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
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 3.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:4904e63e5296…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · + actual - expected · + <str> · - <str>javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-20 · Last seen: 2026-10-20