Find every regex in a codebase, and report which can be driven into catastrophic backtracking
-
Updated
Aug 14, 2026 - Rust
Find every regex in a codebase, and report which can be driven into catastrophic backtracking
Extract every color in a codebase, and say which ones are not in your palette
Extract every hardcoded number in a codebase, so a person can check them
Extract every URL in a codebase, with its protocol and exact position
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
Extract every string in a codebase, with its position, so a person can read them
Check whether a page is scrapeable before the scraper is written, and say when it cannot tell
letools.dev — the hub site for the LE family of VS Code extensions, by nolindnaidoo. Static Next.js + HeroUI on Vercel.
Extract every date and timestamp, and the exact instant each one resolves to
Extract every file path in a codebase, and say whether it still points at anything
Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts
Extract every IP address, CIDR block and MAC, normalized and classified by scope
Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
Find where one dependency is constrained differently across a repository's manifests
Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
Identify the i18n library a project uses, then audit its catalogs by that library's rules
Add a description, image, and links to the letools topic page so that developers can more easily learn about it.
To associate your repository with the letools topic, visit your repo's landing page and select "manage topics."