txt581 B

go.mod Module Manifest (as .txt)

A Go module manifest with separate direct and // indirect require blocks for the fictional tree. Served with a .txt extension because go.mod has no registered media type; the content is verbatim go.mod syntax. Every package, version, hash and licence is fictional — the tree describes nothing real.

Config parsing Conversion testing

Preview — first 22 linestxt

module orchard.example/gateway

go 1.22

require (
	orchard.example/router v2.1.3
	orchard.example/httpcore v1.8.0
	orchard.example/metrics v4.0.0
	orchard.example/cache v0.9.2
	orchard.example/crypto v1.2.0
)

require (
	// indirect dependencies
	orchard.example/logger v3.4.1 // indirect
	orchard.example/retry v1.0.4 // indirect
	orchard.example/jsonpath v2.0.5 // indirect
	orchard.example/yamllite v1.1.7 // indirect
)

// SAMPLE — fictional supply-chain data. Every package, registry, version, hash, licence, advisory identifier and signature in this document is invented.

Specifications

Seed: 51200
Sample Only: true
Ecosystem: Go modules
Go Version: 1.22
Direct Requires: 5
Indirect Requires: 4
Note: served as .txt; go.mod has no registered MIME
Line Endings: LF

Testing contract

Expected to pass

Scenario: Separate direct from indirect requirements in a go.mod file.
Expected result: Parser reports 5 direct and 4 // indirect requires and preserves the tab indentation inside the require blocks.

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.mod Module Manifest (as .txt)” is a deterministic Novus Examples fixture for Config parsing, Conversion testing. 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.