@grum-os/cli@0.3.15
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 27d ago · by lpm-firewall-aiThe package manifest declares a CLI entrypoint but no npm lifecycle hook. The flagged agent setup is an explicit or user-confirmed CLI flow, and the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- The manifest exposes grum.mjs as a CLI entrypoint and declares no install lifecycle hook.
- The flagged source location identifies a Grum-owned Cursor rules file within the agent integration code.
- Cursor setup is conditional on an interactive user choice or an explicit setup action; the inspected code does not establish an unconsented install-time mutation.
Source & flagged code
7 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.15.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.15 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.