@grum-os/cli@0.3.31
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 manifest has no lifecycle scripts, and the flagged process and network behavior is consistent with the user-invoked repository-checking CLI. The Cursor configuration behavior is tied to setup commands, with an interactive consent prompt in the setup path.
Decision evidence
public snapshot- The manifest exposes grum.mjs as the CLI and closes without defining lifecycle scripts.
- The check command runs through the CLI dispatcher and checks a repository against a saved design contract.
- The network client sends requests to the package's Grum service using its configured token.
- The inspected child-process helper runs Git commands in the repository to read repository metadata.
- Cursor setup writes project configuration through init; the interactive setup path asks before proceeding.
- The agent-integration hint identifies a hardcoded Cursor rule path checked by a local path matcher.
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.31.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.31 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.