@grum-os/cli@0.3.32
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 package exposes a CLI without install lifecycle scripts. Source inspection resolves the scanner signals to Git repository checks, Grum API traffic, and user-confirmed project setup, with no confirmed attack surface.
Decision evidence
public snapshot- package.json exposes grum.mjs as the CLI binary and has no lifecycle script.
- The flagged synchronous child process calls run Git inspection commands in a repository and capture their output for repository status and diff checks.
- The HTTP wrapper sends requests to the Grum API origin; the default origin is app.grum.so.
- Cursor agent setup is user-invoked and asks for affirmative confirmation before installation.
- The indicated Cursor rule is a project-local Grum design rule for styling files, not a broad agent configuration destination.
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.32.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.32 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.