@grum-os/cli@0.3.21
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 23d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged process execution reads Git metadata in the repository. The network calls reviewed use the package’s Grum service for login and review reporting; no concrete attack surface was found.
Decision evidence
public snapshot- The manifest exposes grum.mjs as the CLI executable and declares no lifecycle hook.
- The indicated agent-configuration location classifies a Cursor rules path for style analysis; it does not modify agent configuration.
- The process calls run Git commands in the repository directory to read status, branch, and commit metadata.
- Network requests use Grum’s app.grum.so service; login and reporting use its CLI API.
- Cursor setup is offered through an explicit prompt, and the user can skip it.
- The flagged command execution is limited to Git metadata and diff inspection; inspected source does not send command output to an unrelated recipient.
- Reported findings contain project and review metadata sent to the package’s own service, not harvested credentials.
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 · L114Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.21.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.21 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.