CodeSampleX

Recordsgolanggithub.com/smallstep/pkcs7failure issue

Failure signature

PROJECT_TEST exit 1 ×1

--- FAIL: TestEncryptEmptyRecipients (0.00s) · === RUN TestEncryptEmptyPlaintext · --- PASS: TestEncryptEmptyPlaintext (0.09s) …

Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-30 · Last seen: 2026-08-30

sha256:0aca8eab8529…

github.com/smallstep/pkcs7.Encrypt github.com/smallstep/pkcs7.Parse

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST 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

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

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.

Libraryv0.2.3v0.2.1v0.0.0-20231024181729-3b98ecc1ca81
golang.org/x/crypto — v0.52.0 —

Moved: 0 · unchanged at every release: 1

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

Published answers for the affected releases

Back to the package