@grum-os/cli@0.3.43
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 18d ago · by lpm-firewall-aiThe manifest exposes a command-line entrypoint without lifecycle scripts, and the inspected bundle’s process and network behavior is consistent with project checks and requests to Grum. The flagged agent location is an ignore rule; no concrete malicious behavior was found.
Decision evidence
public snapshot- package.json exposes grum.mjs as a CLI binary; the bundle dispatches commands from process arguments.
- The agent-related hint is a rule-path ignore set, not a write to agent configuration.
- The bundle runs git commands against a supplied working directory and sends authenticated API requests to Grum’s fixed service origin.
- The network and process operations appear in CLI command paths; no install lifecycle hook or concrete attack behavior was identified.
- Static hints flag network and child-process APIs, but inspected source shows a Grum service client and git operations rather than command-output exfiltration to an unrelated recipient.
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 · L139Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.43.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.43 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.