@gethookmyapp/cli@0.14.8
HookMyApp CLI, No BS. Just go live.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe malicious scanner classification is not supported by the source: there is no install-time hook or confirmed harvesting/exfiltration chain. However, automatic user-scope Claude MCP setup after login is a concrete agent-extension lifecycle risk under policy.
Decision evidence
public snapshot- dist/cli.js: login success calls maybeInstallClaudeMcp
- dist/cli.js: invokes `claude mcp add-json --scope user`
- MCP configuration supplies a helper that emits an API bearer token
- package.json has no install/preinstall/postinstall hook
- bin/hookmyapp.js only imports the CLI entrypoint
- API tokens are sent to configured HookMyApp API/gateway endpoints
- cloudflared download is user-command-triggered and SHA-256 checked
- scanner child-process matches largely include bundled dependencies and explicit CLI features
- no env/file harvesting or command-output exfiltration found
Source & flagged code
6 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.8.
See all versions of @gethookmyapp/cli for other recorded verdicts.
- Review the evidence and your use of @gethookmyapp/cli@0.14.8 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.