Recordsgolanggithub.com/caddyserver/zerosslfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
List recursive expected 3 entries, got 5: [certs/example.com certs/example.com/site.crt certs/example.com/site.key certs/other.com certs/other.com/site.crt] …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:4ae58c1456b4…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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
- os=linux · runtime=go@1.26 ×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.
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: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/caddyserver/zerossl v0.1.3: Client.GetCertificate, Client.ListCertificates, Client.GenerateEABCredentials 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. HOWzerossl.Client.GetCertificatezerossl.Client.ListCertificateszerossl.Client.GenerateEABCredentialsgo MIT-0 · 2026-08-23