Paths-LE

[Paths-LE Logo]

Paths-LE: Zero Hassle Path Extraction

Pull every file path out of the current file in one keystroke
JavaScript, TypeScript, JSON, YAML, HTML, CSS, TOML, CSV and Environment files — and every other file, by text scan

[Install from VS Code Marketplace] [Open VSX downloads] [paths-le-mcp on npm] [paths-le on npm] [paths-le on crates.io] [LE Tools]

[Paths-LE in VS Code]

Useful? A star or rating is how other developers find it — ★ GitHub · ★ Open VSX · ★ Marketplace

What it does

Open a file, run Paths-LE: Extract Paths, and every file path in the document lands in a new editor — deduplicate and sort it from there. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).

• Import analysis — extract local imports from JS/TS, including multi-line import statements; npm package names are filtered out
• Asset auditing — every src, href, srcset, url(), and @import in HTML/CSS
• Config review — path-like values from JSON/JSONC, YAML, TOML, CSV, and .env files
• Anything else — Python, Go, Markdown, XML, a Dockerfile: no parser, so a text scan finds quoted filenames and any run carrying a path separator

Install

Use it from an AI agent

The same engine runs as an MCP server, so an agent can call it directly instead of you running a command.

[An agent in Claude Code calling the paths-le MCP server]

extract_paths(content, format?, filename?, dedupe?, maxResults?)

Returns every path classified as file, relative, absolute or url, with its 1-based line and column. Paths are reported exactly as written — nothing is resolved against a workspace or touched on disk.

The server takes content and returns data — it reads no files and makes no network requests of its own. Published as paths-le-mcp on npm and as io.github.nolindnaidoo/paths-le in the MCP registry.

{  "mcpServers": {    "paths-le": {      "command": "npx",      "args": ["-y", "paths-le-mcp"]    }  }}

npm install -g paths-le-mcp

{  "mcpServers": {    "paths-le": { "command": "paths-le-mcp" }  }}

echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | npx -y paths-le-mcp

Across a folder or a workspace

Extract reads the document you have open. A scan reads many files from disk and gives one report.

• The whole workspace: run Paths-LE: Extract Paths from Workspace from the command palette.
• One folder: right-click it in the Explorer and choose Extract Paths from Folder, or run Paths-LE: Extract Paths from Folder and pick one.

A project writes the same path in many places, so the report is the distinct paths, the most widely used first, with how often each is written and where:

# Paths-LE workspace report
`my-project` · 4 file(s) read · 2 distinct path(s), 4 occurrence(s) in 3 file(s)
| Path | Occurrences | Files ||---|---|---|| `./lib/util` | 3 | 2 || `./config/app.json` | 1 | 1 |
## `./lib/util` (3)
- `src/a.ts` · **1:20**, **2:20**- `src/b.ts` · **1:20**
## `./config/app.json` (1)
- `deploy.json` · **2:14**
## Could not be read (1)
- `bad.csv`: Invalid CSV: quoted field is never closed (row 1, cell 2)

That is with paths-le.showPositions on. It is off by default, and then each line is the file and how many times the path is in it: src/a.ts (2). The copy on the clipboard follows paths-le.clipboardIncludesPositions, as it does for Extract.

A file its format reader refused is listed with the reason, never passed over. A malformed CSV that holds a path is not the same as a file that holds none.

A scan reports each path as written. It does not resolve symlinks or workspace-relative paths, whatever the resolution settings say: those describe one document on one machine.

What a scan reads. Files come from disk, so an unsaved edit is not seen. A file over the safety size, or one that is not UTF-8 text, is left unread. It stops at 5,000 files or 10,000 listed occurrences. The report ends with a line for each thing it left out, so a short report is never mistaken for a clean project.

What it skips, and how to change that. Three switches are on by default, and each can be turned off on its own in Settings:

Two lists adjust the result without turning a switch off. To skip more, add a pattern to scanExcludes. To read something a switch would skip, add it to scanAlwaysInclude:

{	// Also skip the test fixtures.	"paths-le.workspace.scanExcludes": ["**/fixtures/**"],	// Read the vendored code, though the built-in list skips it.	"paths-le.workspace.scanAlwaysInclude": ["**/vendor/**"]}

Paths-LE: Open Settings opens all of these in the Settings editor.

The settings that shape a scan are under Settings.

The CLI

The same extraction runs from a terminal or an agent loop: a Rust CLI in crate/ of this repository, sharing one corpus with the extension — crate/fixtures/ — so CI fails if the two ever read a document differently. Install it from npm with npm install -g paths-le (or run it with npx paths-le) or from crates.io with cargo install paths-le. Both install the same command and are held to the same output byte for byte.

It also does the half an editor cannot: resolve what it found against the filesystem it is standing in. Every path gets a verdict — exists, missing, escapes the audited tree, non-canonical, or a symlink with its target named.

[paths-le in a terminal]

Install it from npm (paths-le) or from crates.io (paths-le). Both install the same paths-le command.

[paths-le on npm] [paths-le on crates.io]

npm install -g paths-le   # or run it once: npx paths-lecargo install paths-le

paths-le .                    # audit a tree; summary on stderr, JSON on stdout when pipedpaths-le --strict .           # count sloppily-written paths toopaths-le --no-resolve src/    # just list what is written, touch nothingpaths-le mcp                  # the same audit over MCP on stdio

The exit code is the answer: 0 clear · 1 findings · 2 the question was malformed — so paths-le --strict . is a CI step as it stands.

Supported formats

Positions are real source positions for JS/TS, JSON/JSONC, HTML, CSS and the text scan (exact line and column of the path); TOML and YAML positions are located in the source text and can be approximate for repeated identical values; CSV positions are row/cell coordinates. Version strings (1.8.1) and IP addresses are never treated as paths, and data:/javascript: URLs are excluded from HTML/CSS extraction. Bare domains (example.com, www.example.org) are not paths; a name ending in a country-code extension such as docs.rs still is.

The text scan claims a bare name.ext only inside quotes. os.path in a Python file and main.py are the same shape, and no rule short of a dictionary separates them — but source quotes its filenames and does not quote its attribute access, so the quoting does. A YAML scalar holding a shell command (run: node ./scripts/build.js) is one token containing spaces, so no path is claimed from it, exactly as in JSON and TOML.

Commands

No command is bound to a key by default. Give any of them one under Keyboard Shortcuts in the editor.

Settings

Languages

Twelve languages besides English:

German · Spanish · French · Indonesian · Italian · Japanese · Korean · Portuguese (Brazil) · Russian · Ukrainian · Vietnamese · Chinese (Simplified)

Both halves are covered — the manifest (command titles, setting names and descriptions) and everything shown while the extension runs (notifications, the status bar, quick-picks and prompts). The extension follows VS Code's display language, so it matches whatever the editor is already set to; no setting of its own.

Privacy & security

• No network access. The extension never sends data anywhere. The telemetryEnabled setting only writes events to a local Output Channel you can inspect (Paths-LE Telemetry).
• Canonical resolution is opt-in and warned. Resolving symlinks/workspace-relative paths can put absolute filesystem paths into the results document; the extension warns before first use. Leave both resolution.* settings off unless you need them.
• The MCP server holds the same line. It takes content as an argument and returns data: no filesystem access, no network calls, no telemetry. Your agent already has file-read tools, so duplicating them inside the server would add a path-traversal surface for no capability. check:mcp-bundle fails the build if the server ever imports something that could reach either.
• Error notifications redact home directories and credential-shaped fragments.
• One rating prompt, at most twice. On the 3rd successful use the extension asks once whether you would rate it, and once more on the 20th if you chose Later or dismissed it. Don't Ask Again ends it. Setting notificationsLevel to important or silent yourself turns it off. The counts are kept in VS Code's extension storage and nothing is sent anywhere; Rate opens the listing you installed from — the VS Code Marketplace or Open VSX — in your browser.

Documentation

Performance

Median of 7 runs after warmup, on Apple M5 Pro, 24 GB RAM, Node 24.3.0. Inputs are generated by scripts/benchmark.ts rather than checked in, so the sizes above are exactly what was measured. Reproduce with bun run benchmark.

These are machine-specific and are not asserted in CI — a benchmark that gates a build only tells you how busy the runner was.

Testing

554 test cases across 38 files, plus an integration suite that runs in a real VS Code extension host and an end-to-end test that installs the built .vsix into a clean profile.

Generated from a real run — coverage/coverage-summary.json and coverage/test-results.json — by scripts/coverage-readme.js, and bun run coverage:readme:check says whether it has drifted since. Reproduce with bun run test:coverage, and the case count is the one vitest prints.

More from the LE family

Sixteen single-purpose tools for the work in front of every model. Each ships a Rust CLI and an MCP server. One page: letools.dev

Get it out

• String-LE — Extract every string in a codebase, so a person can read them
• Numbers-LE — Extract every hardcoded number in a codebase, so a person can check them
• Units-LE — Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
• Dates-LE — Extract every date and timestamp, and the exact instant each one resolves to
• IDs-LE — Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
• IPs-LE — Extract every IP address, CIDR block and MAC, normalized and classified by scope
• URLs-LE — Extract every URL in a codebase, with its protocol and exact position
• Paths-LE — Extract every file path in a codebase, and say whether it still points at anything
• Colors-LE — Extract every color in a codebase, and say which ones are not in your palette

Check it

• Regex-LE — Find every regex in a codebase, and report which can be driven into catastrophic backtracking
• Versions-LE — Find where one dependency is constrained differently across a repository's manifests
• i18n-LE — Identify the i18n library a project uses, then audit its catalogs by that library's rules
• Scrape-LE — Check whether a page is scrapeable before the scraper is written, and say when it cannot tell

Guard it

• Secrets-LE — Find hardcoded credentials in a codebase, and never print one into the report
• EnvSync-LE — Compare the dotenv files in a tree, and say which keys are missing from which
• Unicode-LE — Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts

Each stands on its own: no shared crate, no published core. Where two of them agree, it is because the same answer was right twice.

Contact — nolindnaidoo.com · GitHub · LinkedIn

Also by nolindnaidoo

Rust — pixelcoords and pixelactions are one loop: pixelcoords answers where, pixelactions acts there. Their own tools, their own voice — not part of the LE family.

• pixelcoords — Freeze your screen, mark regions, get pixel-exact coordinates and crops pixelcoords.dev · crates.io · docs.rs
• pixelactions — Consume human-verified coordinates, perform the interaction, confirm it landed pixelactions.dev · crates.io · docs.rs

License

MIT © nolindnaidoo