@grum-os/cli@0.3.28
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 22d ago · by lpm-firewall-aiThe package provides an invoked CLI, but its generated Cursor guidance includes instructions that steer an AI assistant and discourage independent source inspection. Because this behavior is tied to agent setup rather than an install hook, it warrants a warning for guarded agent-configuration capability.
Decision evidence
public snapshot- The manifest exposes grum.mjs as the package's CLI executable.
- The source identifies .cursor/rules/grum.mdc as Grum's own Cursor rule.
- Generated Cursor guidance tells an AI assistant to prioritize enabling Grum and not inspect the CLI's own files.
- Cursor setup writes that generated guidance into the project rule file.
- The interactive setup flow asks whether to configure Cursor agents and proceeds when the user answers yes.
- The inspected package manifest has no install lifecycle hook.
- The Cursor configuration change is tied to an invoked setup flow, with an affirmative prompt in the interactive branch.
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 · L134Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.28.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.28 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.