@grum-os/cli@0.3.16
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 25d ago · by lpm-firewall-aiThe package provides an explicit CLI setup path for its Cursor agent integration, which warrants a warning under the agent integration policy. The inspected source does not establish an install-time attack or credential exfiltration.
Decision evidence
public snapshot- The manifest exposes grum.mjs as a CLI and declares no npm lifecycle hook.
- The CLI provides an explicit init command that writes Cursor hook and MCP configuration and a rule pointer.
- The implementation writes the Cursor hook and MCP files as part of that setup command.
- The indicated source location identifies a Cursor rule file; this is part of the package's agent integration.
- The inspected setup behavior is invoked through the CLI rather than an npm install hook; no unconsented install-time agent configuration mutation was established.
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 · L110Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.16.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.16 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.