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

What Regex-LE does
A regular expression is easy to write and hard to trust. Regex-LE finds every pattern in the current file, runs one against the document to show real matches with line and column positions and capture groups, and screens each pattern for the shapes that cause catastrophic backtracking. Three commands: extract, test, validate.
What people use it for
Extract
List every regex pattern found in the document, literals and RegExp constructors alike.
Test
Run a found — or manually entered — pattern against the file and see matches with positions and named capture groups.
Validate
Check every pattern for syntax errors and screen it for ReDoS-prone shapes before it reaches production.
Install Regex-LE
VS Code
ext install nolindnaidoo.regex-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.regex-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y regex-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_patterns 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 regex-le-mcpRuns Regex-LE's engine as an MCP server, so an agent can call extract_patterns with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where Regex-LE lives
- VS Code Marketplaceregex-le
- Open VSXfor Cursor and VSCodium
- GitHubsource, issues, changelog
- npmregex-le-mcp
- MCP registryio.github.nolindnaidoo/regex-le
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 URLs from documentation, configs, and code.
Extract date and time data from logs, configs, and code.
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.