Sample
github.com/google/uuid v1.6.0: NewSHA1, NewMD5
Verified sample for golang github.com/google/uuid v1.6.0: NewSHA1, NewMD5. The contract ran on go 1.26 · linux alpine/x64 · docker and passed: uuid.NewSHA1…
sha256:857fda6d3eedbfb535c3154e7ac473bb5944020b7763b63463fb0dad4a4226a6
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
windows 11 x64 go
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-19 |
Case
HOW- Goal
- verify pkg:golang/github.com/google/uuid@v1.6.0
- Packages
- Symbols
-
- github.com/google/uuid.NewSHA1
- github.com/google/uuid.NewMD5
- Created
- 2026-08-18T20:51:57Z
Contract
- uuid.NewSHA1 generates a deterministic Version 5 UUID from a namespace and data
- uuid.NewSHA1 sets Version 5 and RFC4122 variant
- uuid.NewSHA1 produces distinct UUIDs for different input data
- uuid.NewMD5 generates a deterministic Version 3 UUID from a namespace and data
- uuid.NewMD5 sets Version 3 and RFC4122 variant
- uuid.NewSHA1 and uuid.NewMD5 produce 16-byte UUIDs that round-trip with String() and Parse()
Files
- PROMPT.md
- csx.json
- go.mod
- go.sum
- main.go
- spec.json
- test/contract.go
Origin Seeder
anonymous