@grum-os/cli@0.3.34
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 21d ago · by lpm-firewall-aiThe scanner signals are explained by expected CLI behavior: fixed Git metadata checks, authenticated requests to the package-aligned Grum service, and user-directed integration setup. No malicious behavior or unresolved attack surface was identified.
Decision evidence
public snapshot- The manifest exposes grum.mjs as the CLI binary; inspection found no install lifecycle hook.
- The .cursor/rules/grum.mdc reference is a recognized rule path in the bundled analyzer.
- Cursor setup asks before enabling integration, and setup actions follow that user choice.
- Repository checks use fixed git subcommands and collect repository status and revision metadata.
- Authenticated requests use the configured Grum API origin, which defaults to app.grum.so.
- Review requests and reports send findings and Git provenance to the Grum service as part of the CLI workflow.
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.34.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.34 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.