Validate --module names against expansion modules only - #30
Open
elhoim wants to merge 1 commit into
Open
Conversation
The --module argument was validated against every module in /modules (import, export, and expansion alike). This let a valid import/export module name pass validation, then silently match nothing in find_modules_for_type and query nothing, exiting 0 as if it had worked. Validate against get_expansion_modules(modules) instead, and report the mismatch as an unknown expansion module.
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.
Finding 30 (Medium) —
bin/cli.py:890-894Problem
--module names are validated against every module in /modules rather than only expansion modules, so a valid import/export module name passes validation, matches nothing in find_modules_for_type, queries nothing, and exits 0.
Fix
The --module flag was validated against every module returned by /modules (import, export, and expansion alike), not just expansion modules. This let a valid import/export module name (e.g. "ocr") pass validation, then match nothing in find_modules_for_type since that function only scans expansion modules — the command would silently query nothing and exit 0 as if successful. Fixed by validating selected module names against get_expansion_modules(modules) and rewording the error message to make clear only expansion modules are valid here.
Verification
Reproduced against the unmodified code at
9b8c605, then re-checked after the change.Before
After
python bin/cli.py --helpexits 0 and the module still imports cleanly. Verification was performed offline against the pure functions — no runningmisp-modulesinstance is required.Branched from
9b8c605. This PR addresses only this finding; the other findings from the same review are in separate PRs, so they will need rebasing against each other as they merge.🤖 Generated with Claude Code
https://claude.ai/code/session_01DYX4TKA5inzByJ4qGWKjqh