lock1 KB

Gradle Dependency Lockfile

A Gradle dependency lockfile: one `group:artifact:version=configurations` line per fictional module plus the `empty=` line that records configurations resolving to nothing. Every package, version, hash and licence is fictional — the tree describes nothing real.

Config parsing Conversion testing

Preview — first 15 lineslock

# This is a Gradle generated file for dependency locking.
# Manual edits can break the build and are not advised.
# This file is expected to be part of source control.
# SAMPLE — fictional supply-chain data. Every package, registry, version, hash, licence, advisory identifier and signature in this document is invented.
com.orchard.example:example-cache:0.9.2=compileClasspath,runtimeClasspath
com.orchard.example:example-crypto-shim:1.2.0=compileClasspath,runtimeClasspath
com.orchard.example:example-http-core:1.8.0=compileClasspath,runtimeClasspath
com.orchard.example:example-json-path:2.0.5=compileClasspath,runtimeClasspath
com.orchard.example:example-logger:3.4.1=compileClasspath,runtimeClasspath
com.orchard.example:example-metrics:4.0.0=compileClasspath,runtimeClasspath
com.orchard.example:example-retry:1.0.4=compileClasspath,runtimeClasspath
com.orchard.example:example-router:2.1.3=compileClasspath,runtimeClasspath
com.orchard.example:example-yaml-lite:1.1.7=compileClasspath,runtimeClasspath
empty=annotationProcessor

Specifications

Seed: 51200
Sample Only: true
Ecosystem: Gradle
Modules: 9
Configurations: compileClasspath, runtimeClasspath
Line Endings: LF

Testing contract

Expected to pass

Scenario: Parse Gradle's flat key=value lock format including the empty= sentinel.
Expected result: Nine module coordinates load with their configuration lists, and the empty= line is treated as metadata rather than as a module named 'empty'.

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

“Gradle Dependency Lockfile” 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.