@grum-os/cli@0.3.14
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 18d ago · by lpm-firewall-aiThe manifest declares a CLI entrypoint and no lifecycle hooks. The inspected process and network behavior matches repository review and capture functions, with no evidence of unrelated credential transfer or malicious installation behavior.
Decision evidence
public snapshot- package.json exposes grum.mjs as a CLI and contains no npm lifecycle hook.
- The flagged agent configuration location is part of a Cursor rule-path list; the manifest does not run it during installation.
- The CLI reads repository data through git and sends authenticated requests through its Grum API client, consistent with its design-review functions.
- The inspected capture request sends data to the origin associated with the saved Grum session.
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 · L109Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.14.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.14 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.