@grum-os/cli@0.3.47
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 16d ago · by lpm-firewall-aiThe suspicious command and network signals correspond to local Git inspection and the CLI’s review submission flow. The manifest has no install hook, and the inspected agent-related excerpt identifies a project rule path without showing configuration mutation.
Decision evidence
public snapshot- package.json exposes grum.mjs as a CLI and declares no lifecycle script.
- The agent-related code recognizes a project rule file path; this excerpt does not show a write to agent configuration.
- The inspected child-process helper runs local Git commands to read repository state.
- The review request includes project findings and repository provenance, then posts the request through the CLI API.
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 · L150Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.47.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.47 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.