@grum-os/cli@0.3.38
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 20d ago · by lpm-firewall-aiThe source allows an environment-provided API origin and forwards GRUM_TOKEN to it without verifying the token's intended recipient. This creates a conditional credential-exposure risk, while the inspected agent setup is explicitly prompted and does not establish a separate attack.
Decision evidence
public snapshot- The indicated agent location is a local Grum Cursor rule path, and interactive setup asks before installing agent configuration.
- The API origin can be set to any HTTP(S) origin; the built-in default is Grum's app service.
- A GRUM_TOKEN environment value is paired with the selected origin without checking that the token belongs to it; saved credential files are origin-bound.
- Authenticated project lookups pass that token to a request that sends it as a bearer credential to the selected origin.
- The package exposes grum.mjs as its CLI entrypoint.
- The saved-session path accepts credentials only when their stored API origin matches the configured origin. The exposure therefore depends on the separate GRUM_TOKEN environment path and a caller-selected origin.
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.38.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.38 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.