Recordsgolanggithub.com/mholt/acmez/v3v3.1.6
Change the conditions
Current conditions
github.com/mholt/acmez/v3 @v3.1.6ubuntu 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
- 15 / 15
- Contract verifications
- 0 / 1
- Independent reporting peers
- 2
- Last recorded
- 2026-09-04
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v3.1.6
linux
4 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/crypto | v0.50.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/crypto | v0.52.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/net | v0.53.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.55.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| code.pfad.fr/check | v1.1.0 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| github.com/letsencrypt/pebble/v2 | v2.10.0 | 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.
| Library | v3.1.6 | v3.1.2 |
|---|---|---|
| golang.org/x/crypto | v0.52.0 | v0.48.0 |
| golang.org/x/net | v0.55.0 | v0.50.0 |
| code.pfad.fr/check | v1.1.0 | — |
| github.com/letsencrypt/pebble/v2 | v2.10.0 | — |
Moved: 2 · 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
-
observed UNKNOWN exit 1 Evidence gap ×4 v3.1.2 → v3.1.6 os=linux sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-31 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 v3.1.6 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:0ab3a7004d66…node:assert:<n> · throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate