CodeSampleX

Recordsnpm@sigstore/bundle3.1.0@sigstore/bundle.bundleFromJSON

Change the conditions
Fixed
Package version3.1.0 Symbol@sigstore/bundle.bundleFromJSON
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@sigstore/bundle.bundleFromJSON @3.1.0ubuntu glibc · x64 · node 22 · npm 10 · node

2 of 2 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
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-10-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

3.1.0

linux · node@22.23 · moduleSystem=esm · executionContext=node

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 33 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.

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