Skip to content
LE Tools

URLs-LE

Extract URLs from documentation, configs, and code.

FreeOpen sourceMITNo network access
URLs-LE in use: Extract URLs from documentation, configs, and code.

What URLs-LE does

Links rot quietly, and the ones in your code and docs are the hardest to inventory. URLs-LE pulls every URL out of the active document with its real line and column, so a link audit is a list rather than a grep. It reads Markdown, HTML, CSS, JavaScript, TypeScript, JSON, YAML, Properties, TOML, INI and XML, and excludes code blocks and comments where the format defines them.

What people use it for

Link auditing

Every link, autolink and plain URL in Markdown and HTML — code blocks and comments excluded.

Source review

URLs in string literals, template literals and comments across JavaScript and TypeScript.

Config sweep

URLs in JSON strings, YAML values, Java properties, TOML/INI values and XML.

Install URLs-LE

VS Code

ext install nolindnaidoo.urls-le

Open Quick Open (Cmd/Ctrl+P) and paste.

Cursor / VSCodium

cursor --install-extension OffensiveEdge.urls-le

VS Code forks pull from Open VSX, where the namespace is OffensiveEdge.

ZedComing soon

npx -y urls-le-mcp

Works in Zed today — add the command above as a custom MCP server from the agent panel, and extract_urls appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.

AI agents

npx -y urls-le-mcp

Runs URLs-LE's engine as an MCP server, so an agent can call extract_urls with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.

Where URLs-LE lives

The other nine

Extract string values from JSON, YAML, CSV, TOML, INI, and .env — for i18n.

Extract numeric values from JSON, YAML, CSV, TOML, INI, and .env.

Pull every file path out of JS/TS imports, JSON, HTML, CSS, TOML, CSV, and .env files.

Extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, and SVG.

Extract date and time data from logs, configs, and code.

Find, test, and validate the regular expressions in any file — match reports and built-in ReDoS screening.

Check whether a page is actually scrapeable before you burn hours debugging.

Detect and sanitize credentials, tokens, API keys, and private keys locally — before you commit.

Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.