@grum-os/cli@0.3.58
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 2d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and the package’s process and network behavior aligns with its documented design-contract checks and Grum review service. The scanner’s command-execution and output-flow flags are consistent with repository inspection and reporting; no unrelated collection or attack behavior was identified.
Decision evidence
public snapshot- The manifest defines a `grum.mjs` CLI entry and no lifecycle scripts.
- The README describes a repository design-contract checker that can send review findings to Grum.
- The API helper attaches a bearer token to requests made through Grum’s configured API origin.
- The check report payload contains project, branch, commit, and summarized finding fields, including file and line.
- The source uses child processes for repository-scoped `git` operations with timeouts.
- The package reads repository design files as part of its documented checking feature.
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 · L1011Findings
Affected versions and remediation
This report applies to @grum-os/cli@0.3.58.
See all versions of @grum-os/cli for other recorded verdicts.
- Review the evidence and your use of @grum-os/cli@0.3.58 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.