@grum-os/cli@0.2.13
Keep buttons on the Grum Design Contract: a local drift check, Cursor hooks, and an MCP server.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source shows user-invoked agent configuration mutation, which warrants a warning under the supplied policy. Network and command execution support Grum design checks, and no concrete malicious chain was identified.
Decision evidence
public snapshot- package.json exposes the CLI without lifecycle scripts or runtime self-dependencies.
- The explicit grum init cursor command activates agent configuration setup.
- Setup writes repository-local Cursor hooks and MCP configuration.
- Configured hooks run Grum; the default MCP command can fetch Grum through npx --yes.
- Setup generates an always-applied Cursor design rule.
- Stored authentication tokens are checked against the selected service origin.
- No concrete malicious execution or covert credential export was identified.
- Configuration setup is user-invoked and preserves unrelated hook entries.
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 · L195Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.2.13.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.2.13 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.