@grum-os/cli@0.3.51
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 13d ago · by lpm-firewall-aiThe manifest exposes a command-line entrypoint without an install hook. The flagged process and network behavior supports repository checks and requested reporting to the package’s service; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest registers a command-line entrypoint and shows no install lifecycle hook.
- Repository subprocesses invoke Git directly with bounded execution settings.
- The reporting path sends structured project, commit, and finding metadata to Grum when reporting is requested.
- The client uses Grum’s service endpoint for its API requests.
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 · L384Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.51.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.51 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.