Recordsgolanggithub.com/mholt/acmez/v3failure issue
Failure signature
PROCESS_START process start failed Evidence gap ×1
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:c12549970456…
github.com/mholt/acmez/v3.MailReplyChallengeResponse github.com/mholt/acmez/v3.NewCSR github.com/mholt/acmez/v3.OrderParametersFromCSR github.com/mholt/acmez/v3.StaticCSR github.com/mholt/acmez/v3.TLSALPN01ChallengeCert github.com/mholt/acmez/v3/acme.ARIUniqueIdentifier github.com/mholt/acmez/v3/acme.Account github.com/mholt/acmez/v3/acme.Challenge github.com/mholt/acmez/v3/acme.ChallengeTypeDNS01 github.com/mholt/acmez/v3/acme.ChallengeTypeEmailReply00 github.com/mholt/acmez/v3/acme.ChallengeTypeHTTP01 github.com/mholt/acmez/v3/acme.ChallengeTypeTLSALPN01 github.com/mholt/acmez/v3/acme.Identifier github.com/mholt/acmez/v3/acme.Problem github.com/mholt/acmez/v3/acme.RenewalInfo github.com/mholt/acmez/v3/acme.StatusValid
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/mholt/acmez/v3 v3.1.2: acmez.Client This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWacmez.Client MIT-0 · 2026-09-02
- github.com/mholt/acmez/v3 v3.1.2: acme.StatusValid This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/mholt/acmez/v3/acme.StatusValidgo MIT-0 · 2026-08-28
- github.com/mholt/acmez/v3 v3.1.2: acme.Problem This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/mholt/acmez/v3/acme.Problemgo MIT-0 · 2026-08-28