@grum-os/cli@0.3.45
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 17d ago · by lpm-firewall-aiThe scanner’s command execution and network signals are consistent with repository review commands and authenticated requests to the package’s Grum service. The package has no install lifecycle hook, and the inspected agent-related location identifies a Grum rule path rather than an automatic external control-surface change.
Decision evidence
public snapshot- package.json exposes grum.mjs as a CLI entrypoint and has no lifecycle hooks.
- grum.mjs uses a fixed Grum service for its API requests and sends a bearer token only with those requests.
- The launcher runs git commands against the repository to support its review workflow.
- The agent-related path is a Grum rule file used by the launcher.
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 · L149Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.45.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.45 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.