Maven dependency:tree Output
Maven's dependency tree, complete with the [INFO] log prefix that has to be stripped before the tree can be read and the five-part coordinate form Maven uses. Every package, version, hash and licence is fictional: the tree describes nothing real.
[INFO] Scanning for projects... (SAMPLE output — SAMPLE — fictional supply-chain data. Every package, registry, version, hash, licence, advisory identifier and signature in this document is invented.)
[INFO] --- maven-dependency-plugin:3.6.1:tree (default-cli) @ gateway ---
[INFO] com.orchard.example:gateway:jar:4.2.0
[INFO] +-- :jar:orchard-example/router:jar:2.1.3:compile
[INFO] | +-- example-logger:jar:3.4.1:compile
[INFO] | `-- example-retry:jar:1.0.4:compile
[INFO] +-- :jar:orchard-example/http-core:jar:1.8.0:compile
[INFO] | +-- example-logger:jar:3.4.1 deduped:compile
[INFO] | `-- example-json-path:jar:2.0.5:compile
[INFO] +-- example-metrics:jar:4.0.0:compile
[INFO] | `-- example-logger:jar:3.4.1 deduped:compile
[INFO] +-- example-cache:jar:0.9.2:compile
[INFO] | `-- example-yaml-lite:jar:1.1.7:compile
[INFO] | `-- example-json-path:jar:2.0.5 deduped:compile
[INFO] `-- example-crypto-shim:jar:1.2.0:compile
[INFO] BUILD SUCCESS
Specifications
- Seed
- 51200
- Sample Only
- true
- Tool
- mvn dependency:tree (shape)
- Log Prefix
- [INFO]
- Coordinate Form
- group:artifact:packaging:version:scope
- Line Endings
- LF
Testing contract
Reference control- Scenario
- Extract a dependency tree from build-log output rather than from a report file.
- Expected result
- Parser strips the [INFO] prefix, splits five-part coordinates correctly, and ignores the BUILD SUCCESS line instead of treating it as a node.
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
“Maven dependency:tree Output” is a deterministic Testaroo fixture for Log parsing, Graph data, Conversion testing. Access logs and JSON-lines application logs, for testing log parsers, tailers, and ingestion pipelines.
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.
Generated by generation/supply_chain.py. Free for any use, no attribution required, license.
Related files
- graphmlDependency Graph (GraphML)The dependency graph in GraphML, with typed attribute keys for node version, licence and depth and for edge range: the interchange format graph databases and analysis tools import. Every package, version, hash and licence is fictional: the tree describes nothing real.
- mmdDependency Graph (Mermaid Flowchart)The dependency graph as Mermaid, for embedding in Markdown documentation, labelled edges carry the declared range and a classDef highlights the two diamond joins. 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.
- jsonDependency Graph With Diamond Dependencies (JSON)An explicit node/edge dependency graph with in-degree, out-degree and depth precomputed, plus a diamonds array naming the two shared nodes and their parents: the reference answer for any graph builder run against the SBOMs and lockfiles here. Every package, version, hash and licence is fictional: the tree describes nothing real.
- dotDependency Graph With Diamonds (Graphviz DOT)The same diamond graph as Graphviz DOT, with edge labels carrying the declared semver range and the two diamond joins filled, renderable to SVG and diffable against the JSON twin. Every package, version, hash and licence is fictional: the tree describes nothing real.
- mdVersion Conflict and Diamond Report (Markdown)The written explanation of both diamonds in this category (the one that resolves to a single shared node and the peer conflict that forces a nested duplicate) with the four assertions a resolver test should make. Every package, version, hash and licence is fictional: the tree describes nothing real.
