feat(cli): add manus-agent vendor-response subcommand for vendor patch status tracking - #149
Open
manus-use wants to merge 1 commit into
Open
feat(cli): add manus-agent vendor-response subcommand for vendor patch status tracking#149manus-use wants to merge 1 commit into
manus-use wants to merge 1 commit into
Conversation
…h status tracking
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
Wire up the README-documented
manus-agent vendor-responseCLI subcommand that was missing from the actual CLI implementation. This connects the existingtrack_vendor_responsetool function to a proper CLI entry point with text and JSON output modes.What it does
manus-agent vendor-response CVE-2024-3094 manus-agent vendor-response CVE-2024-3094 --output json | jq .vendor_response_stateQueries NVD references, CISA KEV, and VulnCheck KEV to produce a 6-state vendor patch/response classification:
patch_available— confirmed fix releasedpatch_pending— vendor acknowledged, fix in progressworkaround_only— mitigation published, no patch yetinvestigating— vendor acknowledged, status unclearno_patch_expected— won't-fix / EoL / disputedunknown— insufficient dataOutput includes confidence score (0–1), evidence list, and signal summary (NVD ref count, CISA KEV hit, VulnCheck KEV hit, API key presence).
Changes
src/manus_agent/cli.py: Added_build_vendor_response_parser(),_render_vendor_response_text(),_run_vendor_response(), registered"vendor-response"in_SUBCOMMANDSset, and wired dispatch inmain()tests/test_cli_vendor_response.py: 60 fully-mocked tests covering parser validation, text rendering for all 6 states, confidence label thresholds, signal display, evidence rendering, JSON output schema, CVE ID validation/normalization, integration with_classifyinternals, error handling, and edge casesTest results
(Baseline 1158 + 60 new, 0 failures)
Duplicate check
Confirmed NO overlap with existing open PRs:
track_vendor_responsetool function (not CLI wiring)verify-exploitCLI (different subcommand)silent-patchesCLI (different subcommand)cluster-variantsCLI (different subcommand)temporal-priorityCLI (different subcommand)poc-freshnessCLI (different subcommand)sbom-scanCLI (different subcommand)No open or merged PR implements the
vendor-responseCLI subcommand.Motivation
The
vendor-responsesubcommand is documented in README but was never actually wired into the CLI dispatcher. This PR closes that gap, making the tool accessible via the command line as documented.