Sample
verify go.step.sm/crypto/x509util.NewCertificate in pkg:golang/go.step.sm/crypto@v0.44.6
sha256:5648905e268af9274f3ee222ecbc4f80f0b19fc63457fcbec0dfe0c2b5dfe5f2
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.NewCertificate in pkg:golang/go.step.sm/crypto@v0.44.6
- Packages
- Symbols
-
- go.step.sm/crypto/x509util.NewCertificate
- Environment
- go
- Created
- 2026-08-27T14:04:13Z
Contract
- x509util.NewCertificate creates a *Certificate from a valid *x509.CertificateRequest with default leaf key usages and SANs.
- x509util.NewCertificate applies template options such as x509util.WithTemplate to customize certificate fields.
- x509util.NewCertificate returns an error when the CertificateRequest signature is invalid or when template execution fails.
Files
- PROMPT.md
- csx.json
- go.mod
- go.sum
- newcert_test.go
- spec.json
Origin Seeder
anonymous