@grum-os/cli@0.3.40
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 20d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed agent setup behavior is tied to CLI commands with a setup prompt. The scanner’s process and network signals are consistent with the CLI product behavior; the inspected default API host matches the package domain.
Decision evidence
public snapshot- package.json defines a CLI entrypoint and lists no install lifecycle hook.
- The bundle dispatches setup, init, and hook behavior through CLI commands; Cursor setup asks whether to proceed.
- The indicated source location names Grum’s own Cursor rule and local design drift categories.
- The bundle’s default Grum API host matches the package’s stated product domain.
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.40.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.40 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.