@grum-os/cli@0.3.37
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 flagged process, filesystem, and network capabilities belong to the CLI’s setup and service workflows. The inspected sources show no lifecycle-triggered behavior or concrete attack chain.
Decision evidence
public snapshot- package.json exposes grum.mjs as the CLI and declares no lifecycle scripts.
- The Cursor rules path is tracked as a Grum product file; that reference alone does not perform a write.
- Agent configuration is reached through explicit setup commands; init checks project setup conditions before writing project-level hook and MCP files.
- Interactive Cursor agent setup asks the user to affirm before proceeding, with an option to skip.
- The default API origin is Grum’s service; a custom origin must be supplied through GRUM_API_ORIGIN.
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.37.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.37 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.