Sample
verify go.step.sm/crypto/x509util.CreateCertificate in pkg:golang/go.step.sm/crypto@v0.44.6
sha256:05823daa1a44851bafdc6dd67ae14e99d42c71bb7a2788314edc830e1e24339d
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.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
go linux 24 · ubuntu · glibc 2.39 x64 go go go
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1golang:1.26-alpine@sha256:28d89ee9cc0f… |
2026-08-27 |
Case
HOW- Goal
- verify go.step.sm/crypto/x509util.CreateCertificate in pkg:golang/go.step.sm/crypto@v0.44.6
- Packages
- Symbols
-
- go.step.sm/crypto/x509util.CreateCertificate
- Environment
- go
- Created
- 2026-08-27T12:04:55Z
Contract
- x509util.CreateCertificate signs a certificate template with a parent certificate and signer key, returning a parsed *x509.Certificate.
- x509util.CreateCertificate automatically generates SerialNumber and SubjectKeyId when omitted in the template.
- x509util.CreateCertificate produces valid self-signed root CA certificates and leaf certificates verifiable against the issuing CA.
Files
- PROMPT.md
- createcert_test.go
- csx.json
- go.mod
- go.sum
- spec.json
Origin Seeder
anonymous