go.sum Checksum Lines (as .txt)
go.sum content: two h1: lines per fictional module — one for the module zip and one for its go.mod — which is the pairing a verifier must require. Served as .txt because go.sum has no registered media type. Every package, version, hash and licence is fictional — the tree describes nothing real.
orchard.example/router v2.1.3 h1:LYscLAHfzMM6bbL3HPcC+qlvb+8Y25xbosyDr/FXD/q=
orchard.example/router v2.1.3/go.mod h1:hDK/2VTI+G0ZlgL1oXwbNNK8UZYbG9l8cZ+6zPcGjec=
orchard.example/httpcore v1.8.0 h1:xPyOroNx4zAuL0o68VjF9iADGjc8fxwZvMPmFvB4sTN=
orchard.example/httpcore v1.8.0/go.mod h1:KJr6zhIBeLZlk1uuNbFJSFctP4txqtfXwDJaDIMnZWA=
orchard.example/metrics v4.0.0 h1:+SS5D0F4F/2AIGKoxvGLiM/FWws41rXnUdOe9yNN7nU=
orchard.example/metrics v4.0.0/go.mod h1:eZh1+BKI5Mnzw/UNkVMUVLeLB13LSvRbTfABJ5J/wka=
orchard.example/cache v0.9.2 h1:2mA549MOm7C+B9fOJF+TdYYwQ05+KRNB3XZscrar4If=
orchard.example/cache v0.9.2/go.mod h1:ygFawPh8MqvuYq3t/cRbmynQavUEQ0TXnyPA/NejH2z=
orchard.example/crypto v1.2.0 h1:xNNFa7kKXjsAOGwaVGgh4XLwvarCDqoECRkXMeZ8ZsM=
orchard.example/crypto v1.2.0/go.mod h1:h+YsNKeoDVr+9bw6m18bFJyO9umcLI6RaQLRxjl9RrI=
orchard.example/logger v3.4.1 h1:PpjA80CYlIpSpyseBBOrx/C/tsc65zP6fja9EqUhgIV=
orchard.example/logger v3.4.1/go.mod h1:rhwPLyrKkLXLRNL8L5wUQh3O4l68BfloxQKscKzPk8f=
orchard.example/retry v1.0.4 h1:UAZh3y4u1pGwiP/nyBPFp9aq/KFMhIfpFlxdZ4A1y0T=
orchard.example/retry v1.0.4/go.mod h1:HJsvUgIC1NXqZvcQwaR45DywTHPzz84gJiA+8Ikt+AR=
orchard.example/jsonpath v2.0.5 h1:ODfBaKgHnvKs2+y4dkNUmQnsn/W5CE73V1GBsvV+1eU=
orchard.example/jsonpath v2.0.5/go.mod h1:4AUcCBlgNxgsydawhOZZEI4uae6bIG0bKNNni86O6gR=
orchard.example/yamllite v1.1.7 h1:1sVLsqgTMK840aOezor/BQoDdebFIbkFB3okE+l9nfv=
orchard.example/yamllite v1.1.7/go.mod h1:FoMFO3zesOEjdhrky8hjTi+pc1bbnPov8Cgvk0KHmXd=
Specifications
- Seed
- 51200
- Sample Only
- true
- Ecosystem
- Go modules
- Modules
- 9
- Lines Per Module
- 2
- Hash Prefix
- h1:
- Note
- served as .txt; go.sum has no registered MIME
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Validate that every module in go.sum has both a zip and a /go.mod hash line.
- Expected result
- Checker reads 18 lines for 9 modules and reports no module missing its go.mod companion hash.
What is a .txt file?
TXT is a plain-text file containing unformatted character data with no styling or structure beyond line breaks. Its interpretation depends on character encoding, most commonly UTF-8, and on line-ending convention. It is the most universal and portable text container.
How to use this file
Use an example TXT to test encoding detection, line-ending (LF versus CRLF) handling, and any tool that reads or streams raw text input.
How to use this file for testing
“go.sum Checksum Lines (as .txt)” is a deterministic Novus Examples fixture for Config parsing, Conversion testing, Error handling. TOML and INI configuration files with nested sections and typed values — for testing config parsers and loaders.
Documented properties for this file: seed 51200 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
SBOM, lockfile, provenance, and advisory fixtures describe the same fabricated component tree across formats, so a converter or scanner can be diffed against a known answer. Every package name, version, hash, and advisory ID is invented — never treat a finding here as real.
Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.
Related files
- txtRelease SHA256SUMS ManifestThe oldest supply-chain artifact there is: a sha256sum manifest with the exact two-space separator the tool emits, listing a fictional release tarball and its nine dependency archives. Every package, version, hash and licence is fictional — the tree describes nothing real.
- lockCargo.lock (version 3, Legacy)The same fictional Rust tree pinned by a version 3 Cargo.lock, for testing that a reader keys on the declared version rather than assuming the newest format. Every package, version, hash and licence is fictional — the tree describes nothing real.
- lockCargo.lock (version 4)A Rust Cargo.lock in the version 4 format — TOML [[package]] tables with a registry source, a sha256-shaped checksum and a name-only dependencies array that resolves against the other tables. Every package, version, hash and licence is fictional — the tree describes nothing real.
- lockCargo.lock, Truncated — Intentionally CorruptAn intentionally corrupt Cargo.lock: a valid version 4 lockfile cut off inside a [[package]] table so the final key/value pair is incomplete. Small on purpose. Every package, version, hash and licence is fictional — the tree describes nothing real.
- jsonnpm package-lock.json (lockfileVersion 2, Dual Layout)The transitional npm v2 lockfile, which carries BOTH the v3 packages map and the legacy nested dependencies tree describing the same fictional install — the case where a parser must not double-count. Every package, version, hash and licence is fictional — the tree describes nothing real.
- dotDependency Graph With a Cycle (Graphviz DOT)The cyclic plugin graph as DOT, with the three cycle edges highlighted. Graphviz renders it happily, which is exactly why a topological sort must be the thing that rejects it. Every package, version, hash and licence is fictional — the tree describes nothing real.
Generated by generation/supply_chain.py. Free for any use, no attribution required — license.