@grum-os/cli@0.3.11
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 29d ago · by lpm-firewall-aiThe package has a CLI entry point without an install lifecycle hook. Agent configuration changes occur through explicit Grum setup or init behavior, so this is a warning-level agent capability rather than an install-time attack.
Decision evidence
public snapshot- The manifest exposes a user-run CLI and has no install lifecycle hook.
- The flagged agent integration is a Cursor rule path used by Grum.
- The init command accepts Cursor or Codex and requires a linked project unless explicitly run local-only.
- Cursor initialization writes hook and MCP configuration files in the repository.
- Setup requires an explicit command or interactive confirmation; no unconsented npm-time agent configuration mutation is shown.
- The inspected integration is first-party Grum setup, and no malicious payload execution or credential exfiltration was established.
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 · L107Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.11.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.11 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.