@grum-os/cli@0.3.13
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 28d ago · by lpm-firewall-aiThe suspicious scanner signals map to a bundled CLI with command execution and service network calls, but the inspected evidence shows package-aligned behavior and no install-time trigger or unrelated credential destination. Mark clean.
Decision evidence
public snapshot- The manifest exposes `grum.mjs` as a CLI and declares no lifecycle scripts.
- The cited integration location identifies `.cursor/rules/grum.mdc` as a Grum rule path.
- The CLI sends bearer-authenticated requests to the fixed Grum API origin; the inspected code shows no unrelated recipient.
- Setup and capture reset are CLI commands, not install-time triggers.
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 · L107Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.13.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.13 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.