@grum-os/cli@0.3.60
Keep a repository on the design contract reviewed in Grum: a local drift check, review requests, Cursor hooks and an MCP server.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has a legitimate CLI and MCP purpose, and it discloses automatic tool-error reporting with an opt-out. However, its error reports also include recent tool inputs and outputs, a collection detail not disclosed in the README, so this is suspicious runtime telemetry rather than a confirmed malicious attack.
Decision evidence
public snapshot- The manifest exposes a Grum CLI and has no install lifecycle script; its stated purpose is repository design checks and agent integration.
- The MCP wrapper records tool names, inputs, and outputs; inputs are truncated to 600 characters and outputs to 1,500.
- When an MCP tool fails, the error path automatically reports it with the recent tool-call records attached; reports are posted to Grum's feedback endpoint.
- The README mentions tool-error reports and documents a GRUM_FEEDBACK=off opt-out, but does not describe including recent tool inputs and outputs in those reports.
- The package's CLI, MCP server, and feedback feature align with its stated repository design-checking purpose.
- The feedback endpoint is the package's own Grum service, and users can disable feedback and tool-error reports.
- No install-time lifecycle hook or install-time network activity was identified.
Source & flagged code
8 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
grum.mjsView on unpkg · L1011Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.60.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.60 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.