@grum-os/cli@0.3.36
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 package has no install lifecycle hook, and the flagged agent-rule location is part of design-rule classification rather than evidence of an agent configuration write. The network and project-local setup behavior inspected is consistent with the CLI's stated function.
Decision evidence
public snapshot- package.json declares a CLI entrypoint and no install lifecycle hook.
- The flagged agent-rule path is classified alongside design findings; this excerpt does not write agent configuration.
- The CLI writes Cursor hook and MCP files through its project setup path.
- Network requests use the Grum app service and a bearer token.
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.36.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.36 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.