CodeSampleX

Recordsnpm@sigstore/sign3.1.0

Change the conditions
Fixed
Package version3.1.0 Package manageryarn 4
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@sigstore/sign @3.1.0ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

3 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 (3)

Project observations
3 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

3.1.0

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

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:4904e63e5296265c8b41232f4ed23f140584121dba44a579ff68c8909d9fd82d

View exact conditions View failure cluster
Library Version Health Measured there Projects
@sigstore/bundle 3.1.0 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
@sigstore/core 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
@sigstore/protobuf-specs 0.4.3 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
make-fetch-happen 14.0.3 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
proc-log 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
promise-retry 2.0.1 PASS All observations passed contract passed 25 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.

Library4.1.14.1.03.1.0
@sigstore/bundle 4.0.0 4.0.0 3.1.0
@sigstore/core 3.2.1 3.1.0 2.0.0
@sigstore/protobuf-specs 0.5.1 0.5.0 0.4.3
make-fetch-happen 15.0.6 15.0.3 14.0.3
proc-log 6.1.0 6.1.0 5.0.0
@gar/promise-retry 1.0.3 — —
promise-retry — 2.0.1 2.0.1

Moved: 5 · unchanged at every release: 2

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