Skip to content
LE Tools

Colors-LE

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

FreeOpen sourceMITNo network access
Colors-LE in use: Extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, and SVG.

What Colors-LE does

Design systems drift one hard-coded hex at a time. Colors-LE extracts every color from a stylesheet, template or component file — hex, rgb/rgba, hsl/hsla and named colors — then analyses the result: distribution, clusters of near-duplicates, and contrast ratios against WCAG AA and AAA. It reads CSS, SCSS, LESS, Stylus, HTML, JavaScript, TypeScript and SVG.

What people use it for

Palette auditing

Every hex, rgb()/rgba(), hsl()/hsla() and named color across stylesheets, markup and code.

Design-system review

Analyse distribution, cluster similar colors, and spot near-duplicates.

Accessibility checks

Contrast ratios against WCAG AA and AAA via the Validate command.

Install Colors-LE

VS Code

ext install nolindnaidoo.colors-le

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

Cursor / VSCodium

cursor --install-extension OffensiveEdge.colors-le

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

ZedComing soon

npx -y colors-le-mcp

Works in Zed today — add the command above as a custom MCP server from the agent panel, and extract_colors 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 colors-le-mcp

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

Where Colors-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 URLs from documentation, configs, and code.

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.