Recordsgolanggithub.com/prometheus/common
Change the conditions
Current conditions
github.com/prometheus/common @v0.71.0debian glibc · x64 · go 1.26 · go · go
3 of 3 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 (3)
- Project observations
- 4 / 4
- Contract verifications
- 3 / 3
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
3 of 3 passed
Verified — this network ran a contract at this coordinate.
-
github.com/prometheus/common/expfmt
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.71.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang-jwt/jwt/v5 | v5.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/prometheus/client_model | v0.6.2 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/stretchr/testify | v1.12.1 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/net | v0.58.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/oauth2 | v0.36.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/protobuf | v1.36.12 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/alecthomas/kingpin/v2 | v2.4.0 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 3 project-days |
| github.com/julienschmidt/httprouter | v1.3.0 | PASS All observations passed | contract passed | 3 project-days |
| github.com/munnerz/goautoneg | v0.0.0-20191010083416-a7dc8b61c822 | PASS All observations passed | contract passed | 3 project-days |
| github.com/mwitkow/go-conntrack | v0.0.0-20190716064945-2f068394615f | PASS All observations passed | contract passed | 3 project-days |
| go.yaml.in/yaml/v2 | v2.4.4 | PASS All observations passed | contract passed | 3 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: 10 · unchanged at every release: 12
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.