@grum-os/cli@0.3.22
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-aiNo install-time attack or command-output exfiltration was established; the outbound report contains repository identifiers and summarized findings. The explicit agent setup path modifies Cursor configuration, which merits a capability warning.
Decision evidence
public snapshot- The manifest exposes grum.mjs as a CLI for repository checks, Cursor hooks, and an MCP server.
- The indicated Cursor rule path is recognized as a Grum-owned rule and excluded from contract rule results.
- The setup flow asks whether to configure Cursor, and the setup command dispatches to that flow.
- The Cursor initializer writes repository hook and MCP configuration files and manages Grum’s rule file.
- The check report sends project, branch, commit, and summarized finding details to Grum.
- The flagged process use invokes Git through execFileSync, without shell execution.
- The manifest declares no install lifecycle scripts; the configuration behavior requires running the CLI setup or init command.
- The inspected source provides no evidence that command output is sent to the service.
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.22.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.22 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.