@grum-os/cli@0.3.59
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 2d ago · by lpm-firewall-aiThe flagged process and network behavior supports Grum's repository review features. Its background feedback reporting is disclosed, limited to Grum-related summaries and tool reports, and has a documented opt-out.
Decision evidence
public snapshot- The README describes Grum as checking repository design tokens and UI designs against a team-reviewed contract.
- The README discloses background feedback summaries and failed-tool reports, describes the data included and its sanitization, and documents GRUM_FEEDBACK=off.
- The source sends feedback to Grum's /api/cli/feedback endpoint and supports disabling it through GRUM_FEEDBACK or DO_NOT_TRACK.
- The README says checks can be posted to Grum, and documents when CI and report flags do so.
- MCP tool failures can automatically queue reports containing recent Grum tool calls; this is disclosed in the README and can be disabled.
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 · L1011Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.59.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.59 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.