Versions-LE
Find where one dependency is constrained differently across a repository's manifests
The command-line tool and its MCP server are written and tested. The VS Code extension is not written yet, so there is nothing to install from the Marketplace or Open VSX — those links appear here when it ships rather than before.
No editor in the loop? versions-le mcp runs the same engine as an MCP server, so an agent can call compare_versions over stdio, with no editor and no Node, and cargo install versions-le puts the same check in a terminal. Every way to install it.
What Versions-LE does
The build broke because one crate asks for serde 1.0.200 and another asks for serde 2. Or it did not break, and will, because CI has been running on a toolchain below the minimum a manifest declares. Versions-LE reads the version constraints across package.json, Cargo.toml, pyproject.toml, go.mod and GitHub workflow files, then reports where the same dependency is constrained inconsistently. Two constraints no single version can satisfy is an error, decided by interval arithmetic rather than string comparison; different but satisfiable is a warning; a floating pin is information. Comparison never crosses an ecosystem, and a grammar it does not model is named in the report rather than approximated into a range.
What people use it for
Fail before CI does
A pair of constraints no single version satisfies is an error and a non-zero exit, so the build stops before the deploy does.
Catch CI below the floor
A workflow toolchain that has drifted under the minimum version a manifest declares is the failure nobody notices until a release.
Diff against a baseline
The report carries no timestamp, so two runs over an unchanged tree produce identical output and a review can diff them.
Install Versions-LE
Command lineComing soon
cargo install versions-leNot on crates.io yet — v0.1.3 builds from the repository today, and this command starts working the day it publishes. Follow the repository.
VS CodeComing soon
ext install nolindnaidoo.versions-leThe extension is not written yet, so this id resolves to nothing on the Marketplace. It is the id it will take. Follow the repository.
Cursor / VSCodiumComing soon
cursor --install-extension OffensiveEdge.versions-leSame again for the forks, which resolve Open VSX rather than the Marketplace. Follow the repository.
Zed
versions-le mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and compare_versions appears in its tool list. There is no one-click listing in Zed's extension registry yet.
AI agents
versions-le mcpRuns Versions-LE's engine as an MCP server over stdio, so an agent can call compare_versions with no editor and no Node. The binary is the server — there is nothing else to install.
Where it ships
One engine, 6 places to get it. The ids differ by registry — copy the one for the editor you use.
VS Code Marketplace
VS Code itselfnolindnaidoo.versions-leOpenthe extension is not written yet — this links the sourceOpen VSX
Cursor, Windsurf, VSCodium and the other forksOffensiveEdge/versions-leOpenthe extension is not written yet — this links the sourceMCP server
the same engine, callable by an agent with no editor in the loopversions-le mcpOpenshipped by the binary, not by npm — no package to link yetZed
as a custom MCP server todayversions-le mcpOpenno listing yet — this links Zed’s instructions for adding it by hand
Where Versions-LE lives
- GitHubsource, issues, changelog
- MCP registryio.github.nolindnaidoo/versions-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 file path in a codebase, and say whether it still points at anything
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
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