@grum-os/cli@0.3.3
Keep code on your design contract: a local drift check, review requests, Cursor hooks and an MCP server.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource inspection supports a warning for explicit CLI agent configuration and subsequent unpinned package execution. The absence of install hooks and the package-aligned reporting flow do not support blocking as malicious.
Decision evidence
public snapshot- The manifest exposes grum.mjs as the CLI and contains no lifecycle scripts or runtime self-dependency.
- CLI setup writes repository Cursor hooks, MCP configuration, and a rule that guides agent behavior.
- Interactive setup offers a consent prompt; noninteractive setup also configures Cursor when its directory exists.
- Generated MCP and pre-commit commands use unpinned npx --yes, allowing later package resolution without another installation prompt.
- The flagged location only identifies the Grum rule path; configuration mutation occurs elsewhere in the CLI.
- Saved credentials are bound to their API origin; the flagged command-output transmission reports the Git commit with design-check results.
- No automatic npm installation mutation or concrete malicious attack was identified.
- Configuration helpers preserve unrelated hooks and MCP servers, and support removing Grum 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 · L260Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.3.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.3 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.