@grum-os/cli@0.3.20
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-aiThe scanner's execution and network signals resolve to CLI design-check functionality, metadata reporting gated by explicit options, and agent setup behavior. The inspected source does not establish covert collection, credential disclosure, or unconsented configuration changes.
Decision evidence
public snapshot- package.json exposes grum.mjs as the grum CLI executable.
- The required agent-integration location maps a Cursor rule path to Grum's design-rule classifier.
- Cursor agent setup offers a yes/no choice, then writes Cursor hook and MCP configuration files.
- The report request sends project, branch, commit, source, counts, and finding metadata to Grum.
- The reporting caller requires the --ci or --report option.
- The configured service endpoint is https://app.grum.so.
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.20.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.20 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.