lock735 B

Gemfile.lock (Bundler)

A Bundler lockfile in its indentation-significant block format — specs nested under GEM, transitive requirements nested one level deeper, and the BUNDLED WITH version on its own indented line. Every package, version, hash and licence is fictional — the tree describes nothing real.

Config parsing Conversion testing Error handling

Preview — first 34 lineslock

GEM
  remote: https://gems.orchard.example/
  specs:
    example-cache (0.9.2)
      example-yaml-lite (~> 1.1)
    example-crypto-shim (1.2.0)
    example-http-core (1.8.0)
      example-logger (~> 3.4)
      example-json-path (~> 2.0)
    example-json-path (2.0.5)
    example-logger (3.4.1)
    example-metrics (4.0.0)
      example-logger (~> 3.4)
    example-retry (1.0.4)
    example-router (2.1.3)
      example-logger (~> 3.4)
      example-retry (~> 1.0)
    example-yaml-lite (1.1.7)
      example-json-path (~> 2.0)

PLATFORMS
  ruby
  x86_64-linux

DEPENDENCIES
  example-cache (~> 0.9)
  example-crypto-shim (~> 1.2)
  example-http-core (~> 1.8)
  example-metrics (~> 4.0)
  example-router (~> 2.1)

BUNDLED WITH
   2.5.6

Specifications

Seed: 51200
Sample Only: true
Ecosystem: Bundler
Gems: 9
Sections: GEM, PLATFORMS, DEPENDENCIES, BUNDLED WITH
Indentation: significant
Line Endings: LF

Testing contract

Expected to pass

Scenario: Parse a lockfile where nesting depth, not punctuation, carries the graph.
Expected result: Reader distinguishes the 9 specs from their nested requirement lines and reports 5 top-level DEPENDENCIES.

What is a .lock file?

A .lock file pins the exact dependency graph a package manager resolved, so a later install reproduces it byte for byte. Cargo.lock and Poetry's poetry.lock use TOML, Gemfile.lock and yarn.lock use their own line-oriented grammars, and all of them record resolved versions, source registries, integrity hashes, and the transitive edges between packages. It is committed alongside the human-edited manifest, which states ranges rather than exact versions.

How to use this file

Use an example .lock file to test dependency parsers, SBOM generators, and vulnerability scanners, verifying that transitive dependencies and integrity hashes are read correctly and that a pinned version is never confused with the range declared in the manifest.

How to use this file for testing

“Gemfile.lock (Bundler)” 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.