feat(tools): get_version_range — affected version range resolver + CLI subcommand (+79 tests) - #130
Open
manus-use wants to merge 1 commit into
Open
feat(tools): get_version_range — affected version range resolver + CLI subcommand (+79 tests)#130manus-use wants to merge 1 commit into
manus-use wants to merge 1 commit into
Conversation
manus-use
pushed a commit
that referenced
this pull request
Jul 18, 2026
manus-use
pushed a commit
that referenced
this pull request
Jul 18, 2026
manus-use
force-pushed
the
feat/cli-version-range
branch
from
July 18, 2026 00:18
cb4ce91 to
5484c26
Compare
manus-use
force-pushed
the
feat/cli-version-range
branch
from
August 8, 2026 00:07
5484c26 to
d69b01b
Compare
…I subcommand (+79 tests)
manus-use
force-pushed
the
feat/cli-version-range
branch
from
August 9, 2026 16:09
d69b01b to
3dfe4ff
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the
manus-agent version-rangeCLI subcommand andget_version_rangetool — a README-documented-but-completely-unimplemented feature gap.Resolves a CVE to its affected version ranges by combining:
versionStartIncluding/ExcludingandversionEndIncluding/Excludingmatch criteriaintroduced/fixedversion events from PyPI, npm, Maven, Go, RustSec, etc.Outputs structured vulnerable ranges, affected ecosystems, and the first-patched version.
Usage
manus-agent version-range CVE-2021-44228 manus-agent version-range CVE-2021-44228 --ecosystem pypi manus-agent version-range CVE-2021-44228 --output json | jq .first_patchedFeatures
--ecosystem {auto,pypi,npm,maven,go,crates.io,rubygems,nuget,packagist}Test Coverage
79 fully-mocked tests covering:
Full suite: 1237 passed, 0 failures (baseline 1158 + 79 new)
Files Changed
src/manus_agent/tools/get_version_range.py— new tool modulesrc/manus_agent/cli.py— CLI dispatch + parser +_SUBCOMMANDSentrytests/test_version_range.py— 79 testsDuplicate Check
Checked all 50 open PRs (#134–#183) and 30 merged PRs — no overlap. Closest PRs:
get_osv_data— single CVE OSV query (we build on top of it conceptually but with a different tool that combines NVD CPE + OSV and adds ecosystem filtering/inference)cve-enrich— multi-source enrichment (different purpose: enriches metadata, doesn't resolve version ranges)blast-radius— dependency impact (different axis: downstream dependents, not upstream version ranges)Design Decisions
requestsalready in the project)TOOL_SPEC,log_tool_output_size, CLI parser structure