@gethookmyapp/cli@0.14.11
HookMyApp CLI, No BS. Just go live.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo concrete malicious install-time or unrelated exfiltration chain was found. The automatic post-login AI-agent extension setup is a real, user-scoped lifecycle risk and warrants a warning under policy.
Decision evidence
public snapshot- dist/cli.js auto-runs Claude MCP setup after successful login when `claude` is installed.
- Setup invokes `claude mcp add-json --scope user hookmyapp` with an HTTP MCP endpoint and token-producing headers helper.
- The installed MCP helper executes this CLI's hidden `mcp-headers` command to expose a valid bearer token.
- package.json has no install, preinstall, or postinstall lifecycle hook.
- Claude mutation is gated by an explicit user login, scoped to the named `hookmyapp` MCP server, and targets HookMyApp's API.
- Other network use is package-aligned API/auth, opt-out telemetry, and error reporting; no arbitrary env or command-output exfiltration was found.
Source & flagged code
7 flaggedSource appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L48Source executes local commands and sends command output to an external endpoint.
dist/cli.jsView on unpkg · L48Findings
Affected versions and remediation
This report applies to @gethookmyapp/cli@0.14.11.
See all versions of @gethookmyapp/cli for other recorded verdicts.
- Review the evidence and your use of @gethookmyapp/cli@0.14.11 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.