registry / @grum-os/cli / 0.3.29

@grum-os/cli@0.3.29

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 22d ago · by lpm-firewall-ai

Source inspection found an executable CLI without install hooks. Its flagged process, network, and agent configuration behavior is tied to repository review and explicit setup or request commands, with no concrete malicious behavior established.

Static reason

One or more suspicious static signals were detected.

Trigger

Users invoke CLI commands such as setup or request; there is no package install hook.

Impact

No unconsented credential transfer, destructive behavior, or malicious agent control change was established.

Mechanism

The CLI uses Git for repository inspection, sends review data to the Grum service, and can write repository-local agent configuration during setup.

AI rationale

Evidence

.cursor/hooks.json.cursor/mcp.json.cursor/rules/grum.mdc

Network endpoints1

app.grum.so

Decision evidence

public snapshot

AI called this Clean at 96.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The manifest exposes a command-line executable and declares no install lifecycle hook.
Agent setup is an explicit command that writes repository-local Cursor configuration files.
The indicated agent location is a repository Cursor rule file, and the code excludes that rule from rule text sent upstream.
The child-process helper runs Git commands in the repository with bounded output; it does not run arbitrary shell commands.
The review command sends issue details and optional capture data to Grum through its authenticated API.
The API origin accepts only HTTP or HTTPS; saved credentials are used only when their recorded origin matches the selected origin, while the token environment variable is an explicit caller setting.

Evidence against

Static hints flagged network, environment-variable, and child-process use; inspection tied these to the Grum API, explicit configuration, and repository Git operations.

Behavioral surface

Source

ChildProcessEnvironmentVarsNetworkWebSocket

Source & flagged code

8 flagged

grum.mjsView file

136${t.fix}`:""}`).join(` L137: `)}function Eg(e,t,n,r){let o=e?.profile,s=o?.info_cache;if(!s||typeof s!="object")return null;let i=new Set([...n,...r==="store"?[Nl]:[]]),l=Object.keys(s).sort((a,c)=>a===o?.last... L138: `,{mode:384}),o$(n,384)}function Ng(e,t=Zn()){a$(zl(e,t),{force:!0})}function Fg(e=Zn()){let t=Jr.join(Ns(e),"credentials"),n;try{n=i$(t).filter(r=>r.endsWith(".json"))}catch{retur...

High

Child Process

Package source references child process execution.

grum.mjsView on unpkg · L136

134L135: ${yg(n,!1,!1,s)}`}}var Ll="Grum refreshes review decisions before each MCP check or review-status lookup. If it cannot refresh, current review statuses and blocking findings are un... L136: ${t.fix}`:""}`).join(` L137: `)}function Eg(e,t,n,r){let o=e?.profile,s=o?.info_cache;if(!s||typeof s!="object")return null;let i=new Set([...n,...r==="store"?[Nl]:[]]),l=Object.keys(s).sort((a,c)=>a===o?.last... L138: `,{mode:384}),o$(n,384)}function Ng(e,t=Zn()){a$(zl(e,t),{force:!0})}function Fg(e=Zn()){let t=Jr.join(Ns(e),"credentials"),n;try{n=i$(t).filter(r=>r.endsWith(".json"))}catch{retur...

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

grum.mjsView on unpkg · L134

Findings

4 High2 Medium6 Low

HighChild Processgrum.mjs

HighSame File Env Network Executiongrum.mjs

HighCommand Output Exfiltrationgrum.mjs

HighTrigger Reachable Command Output Exfiltrationgrum.mjs

MediumNetwork

MediumEnvironment Vars

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencegrum.mjs

Affected versions and remediation

This report applies to @grum-os/cli@0.3.29.

See all versions of @grum-os/cli for other recorded verdicts.

Review the evidence and your use of @grum-os/cli@0.3.29 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: 2026-10-14 06:07:51.843Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / @grum-os/cli / 0.3.29

@grum-os/cli@0.3.29

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 22d ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.

Trigger

Users invoke CLI commands such as setup or request; there is no package install hook.

Impact

No unconsented credential transfer, destructive behavior, or malicious agent control change was established.

Mechanism

The CLI uses Git for repository inspection, sends review data to the Grum service, and can write repository-local agent configuration during setup.

AI rationale

Evidence

.cursor/hooks.json.cursor/mcp.json.cursor/rules/grum.mdc

Network endpoints1

app.grum.so

Decision evidence

public snapshot

AI called this Clean at 96.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The manifest exposes a command-line executable and declares no install lifecycle hook.
Agent setup is an explicit command that writes repository-local Cursor configuration files.
The indicated agent location is a repository Cursor rule file, and the code excludes that rule from rule text sent upstream.
The child-process helper runs Git commands in the repository with bounded output; it does not run arbitrary shell commands.
The review command sends issue details and optional capture data to Grum through its authenticated API.
The API origin accepts only HTTP or HTTPS; saved credentials are used only when their recorded origin matches the selected origin, while the token environment variable is an explicit caller setting.

Evidence against

Static hints flagged network, environment-variable, and child-process use; inspection tied these to the Grum API, explicit configuration, and repository Git operations.

Behavioral surface

Source

ChildProcessEnvironmentVarsNetworkWebSocket

Source & flagged code

8 flagged

grum.mjsView file

High

Child Process

Package source references child process execution.

grum.mjsView on unpkg · L136

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

grum.mjsView on unpkg · L134

Findings

4 High2 Medium6 Low

HighChild Processgrum.mjs

HighSame File Env Network Executiongrum.mjs

HighCommand Output Exfiltrationgrum.mjs

HighTrigger Reachable Command Output Exfiltrationgrum.mjs

MediumNetwork

MediumEnvironment Vars

LowHigh Entropy Strings

LowUrl Strings

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencegrum.mjs

Affected versions and remediation

This report applies to @grum-os/cli@0.3.29.

See all versions of @grum-os/cli for other recorded verdicts.

Review the evidence and your use of @grum-os/cli@0.3.29 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: 2026-10-14 06:07:51.843Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.