@grum-os/cli@0.3.52
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 12d ago · by lpm-firewall-aiThe manifest exposes a CLI entrypoint without lifecycle hooks. Source inspection found Grum service reporting with redaction and an opt-out, but no confirmed attack behavior.
Decision evidence
public snapshot- package.json declares grum.mjs as the CLI entrypoint; no lifecycle hook is declared.
- The bundled CLI sends feedback to its configured Grum service, app.grum.so.
- Feedback and error text is redacted and length-limited before it is recorded or included in reports; GRUM_FEEDBACK=off and DO_NOT_TRACK opt out.
- The automatic crash path queues a sanitized error report when the CLI exits with an error.
- The network and process-execution signals are consistent with a CLI that contacts its own service and runs local Git or browser commands; inspected source did not establish command-output exfiltration or another attack.
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 · L642Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.52.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.52 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.