@grum-os/cli@0.3.30
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 21d ago · by lpm-firewall-aiThe manifest exposes a CLI entrypoint without lifecycle hooks, and the inspected agent setup behavior is command-invoked. Network and process operations are consistent with the package's Grum workflow; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json maps the grum executable to grum.mjs and contains no lifecycle hook.
- The required Cursor rule location classifies an internal Grum rule path and design finding categories.
- Cursor setup is an explicit CLI operation that checks for a linked project before writing configuration.
- The CLI dispatches commands from process arguments; capture requests use the configured Grum API origin and send a bearer token to its capture endpoint.
- The process and network signals fit local CLI operations and requests to Grum's API; inspected source did not establish credential forwarding to an unrelated recipient or another attack chain.
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 · L137Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.30.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.30 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.