@grum-os/cli@0.3.39
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 20d ago · by lpm-firewall-aiThe package is a CLI with no install lifecycle script, and the reviewed network behavior is tied to its user-invoked features. The scanner’s command and network signals do not establish an attack.
Decision evidence
public snapshot- The manifest exposes grum.mjs as a CLI and contains no npm lifecycle script.
- The bundled source excludes the designated Cursor rule from collected repository rules.
- The request command sends review details and Git state to Grum as part of a review request.
- Check reports are sent only with --ci or --report, through an authenticated request to Grum.
- The scanner flags command output and network primitives, but the inspected callers tie them to CLI features and package-aligned requests.
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 · L137Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.39.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.39 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.