@grum-os/cli@0.3.41
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 19d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the bundled executable dispatches CLI commands. Inspected process, network, and agent-configuration behavior is consistent with user-invoked product features; the scanner signals alone do not establish an attack.
Decision evidence
public snapshot- package.json defines grum.mjs as the CLI entrypoint and declares no lifecycle hooks.
- grum.mjs dispatches operations by the command supplied on the command line.
- The Grum API client sends bearer credentials to the configured Grum origin; the default origin is app.grum.so.
- Agent configuration changes are performed through the explicit init command.
- The indicated agent-configuration search location contains a rule-path set, not an agent configuration write.
- The bundle includes child-process execution, Git inspection, browser capture, and network requests; inspected callers tie these to CLI features and Grum service 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 · L137Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.41.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.41 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.