@grum-os/cli@0.3.50
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 14d ago · by lpm-firewall-aiThe executable is a user-run CLI, with no manifest lifecycle hook. Inspected network requests target the Grum service and support review or capture flows; the scanner’s combined command and network indicators do not establish malicious behavior.
Decision evidence
public snapshot- The manifest exposes a single Grum CLI entrypoint and declares no lifecycle hook.
- The CLI’s default service endpoint is Grum’s app host.
- Review requests prompt before sending, with an option to skip; capture data is sent to the Grum API as part of the capture flow.
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.50.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.50 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.