Skip to content
Testaroo
txt507 B

npm ls Dependency Tree (Text)

The console tree with box-drawing characters and `deduped` markers on repeat visits: the output people paste into issues, and a genuine test of whether a scraper handles non-ASCII tree glyphs. Every package, version, hash and licence is fictional: the tree describes nothing real.

Preview, first 14 linestxt
@orchard-example/gateway@4.2.0
├── @orchard-example/router@2.1.3
│   ├── example-logger@3.4.1
│   └── example-retry@1.0.4
├── @orchard-example/http-core@1.8.0
│   ├── example-logger@3.4.1 deduped
│   └── example-json-path@2.0.5
├── example-metrics@4.0.0
│   └── example-logger@3.4.1 deduped
├── example-cache@0.9.2
│   └── example-yaml-lite@1.1.7
│       └── example-json-path@2.0.5 deduped
└── example-crypto-shim@1.2.0

Specifications

Seed
51200
Sample Only
true
Tool
npm ls (shape)
Drawing
box-drawing characters
Deduped Markers
true
Encoding
UTF-8
Line Endings
LF

Testing contract

Reference control
Scenario
Parse an indented console tree that uses UTF-8 box-drawing characters.
Expected result
Scraper recovers the same parent/child edges as the JSON tree and treats lines marked `deduped` as back-references rather than as new nodes.

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

“npm ls Dependency Tree (Text)” 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 · UTF-8 · 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.