@grum-os/cli@0.3.35
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 21d ago · by lpm-firewall-aiThe inspected source shows first-party agent setup that is activated by an explicit CLI command and writes project-local configuration. This supports a warning for agent integration capability, not a publish block.
Decision evidence
public snapshot- The manifest declares a CLI binary and no install lifecycle script.
- Running `grum init` can add project-local agent hook and MCP configuration files.
- The configured hooks and MCP server invoke Grum CLI commands, including a command pinned to the latest release.
- The supplied agent-configuration location is part of CSS rule analysis, not agent configuration code.
- The setup behavior requires an explicit CLI command; the inspected code does not establish an install-time configuration change.
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 · L137Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.35.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.35 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.