Is Repowise MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
1 medium
- Code scan647 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Findings (1)
- mediumsubprocess with shell=True
exec.shell-truerepowise-0.17.1/packages/cli/src/repowise/cli/commands/distill_cmd.py: …nd_str = _render_command(command) # shell=True on purpose: the user's own command may …
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Repowise does
- SrclightDeep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.not reviewedEstablishedA
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
- SoloMDRead and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.not reviewedEstablishedB