Recordsnpm@sigstore/bundle3.1.0bundleFromJSON
Change the conditions
Current conditions
bundleFromJSON @3.1.0debian 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-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.1.0
linux · node@22.23 · executionContext=node · moduleSystem=esm
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:4904e63e5296265c8b41232f4ed23f140584121dba44a579ff68c8909d9fd82d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @sigstore/protobuf-specs | 0.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 31 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.1.0 |
|---|---|---|
| @sigstore/protobuf-specs | 0.5.0 | 0.4.3 |
Moved: 1 · 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 PROJECT_TEST exit 1 ERR_ASSERTION ×1 3.1.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-18 · Last seen: 2026-10-18
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 3.1.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.1.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:ccb20bbc5842…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · + actual - expected · + undefined · - <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 UNKNOWN exit 1 Evidence gap ×1 3.1.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:5cb8e084fdab…<path>:<n> · throw new error_1.UnsignedMetadataError(`${delegatedRole} was signed by ${signingKeys.size}/${role.threshold} keys`); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18Diagnostic re-verification candidate