Paths-LE
Extract every file path in a codebase, and say whether it still points at anything
No editor in the loop? npx -y paths-le-mcp runs the same engine as an MCP server, so an agent can call extract_paths with nothing else installed, and cargo install paths-le puts the same check in a terminal. Every way to install it.
What Paths-LE does
A path in an import, an asset reference or a config value is a dependency you cannot see until something breaks. Paths-LE extracts every file and directory path from the active document and classifies each one, so a refactor or an asset audit starts from a list rather than a search. It reads JS/TS imports including multi-line statements, HTML and CSS references, and JSON, TOML, CSV and .env values.
What people use it for
Import analysis
Extract local imports from JS/TS, including multi-line statements — npm package names are filtered out.
Asset auditing
Every src, href, srcset, url() and @import in your HTML and CSS.
Config review
Path-like values from JSON, JSONC, TOML, CSV and .env files.
5 commands in the palette
Open the command palette and type the name. Nothing is bound to a shortcut by default — the editor's keymap is the user's, not ours.
paths-le.extractPathspaths-le.postProcess.dedupepaths-le.postProcess.sortpaths-le.openSettingspaths-le.helpInstall Paths-LE
VS Code
ext install nolindnaidoo.paths-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.paths-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
Zed
npx -y paths-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_paths appears in its tool list. There is no one-click listing in Zed's extension registry yet.
AI agents
npx -y paths-le-mcpRuns Paths-LE's engine as an MCP server, so an agent can call extract_paths with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where it ships
One engine, 6 places to get it. The ids differ by registry — copy the one for the editor you use.
Zed
built from Rust in the tool repopaths-leOpenno listing yet — this links Zed’s instructions for adding it by hand
Where Paths-LE lives
- VS Code Marketplacepaths-le
- Open VSXfor Cursor and VSCodium
- npmpaths-le-mcp
- GitHubsource, issues, changelog
- MCP registryio.github.nolindnaidoo/paths-le
The other 15
Extract every string in a codebase, with its position, so a person can read them
Extract every hardcoded number in a codebase, so a person can check them
Extract every color in a codebase, and say which ones are not in your palette
Extract every URL in a codebase, with its protocol and exact position
Extract every date and timestamp, and the exact instant each one resolves to
Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
Extract every IP address, CIDR block and MAC, normalized and classified by scope
Find every regex in a codebase, and report which can be driven into catastrophic backtracking
Check whether a page is scrapeable before the scraper is written, and say when it cannot tell
Find where one dependency is constrained differently across a repository's manifests
Identify the i18n library a project uses, then audit its catalogs by that library's rules
Find hardcoded credentials in a codebase, and never print one into the report
Compare the dotenv files in a tree, and say which keys are missing from which
Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts