@grum-os/cli@0.3.57
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 8d ago · by lpm-firewall-aiThe scanner’s command-output exfiltration signal is not supported by the inspected data flow: local Git output is captured, while the report request contains check metadata. The inspected network behavior is aligned with the Grum CLI service, with no concrete attack surface established.
Decision evidence
public snapshot- The manifest identifies a Grum repository-check CLI and names grum.mjs as its entrypoint.
- The client uses app.grum.so by default and accepts only an HTTP or HTTPS API origin from configuration.
- The report request sends project, branch, commit, and finding summary fields to Grum’s report endpoint.
- The inspected network helper uses the configured Grum API origin and can attach the stored Grum token; the inspected report call sends check metadata rather than command output.
- Git subprocess helpers run local repository queries with captured output, but the inspected report construction does not include that output.
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 · L1011Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.57.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.57 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.