@gethookmyapp/cli@0.14.22
HookMyApp CLI, No BS. Just go live.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI’s MCP credential flow targets its configured HookMyApp API, and no forwarding of unrelated credentials or other concrete attack behavior was found. The package has no install hook; its telemetry is disclosed with a disable setting.
Decision evidence
public snapshot- The manifest has no install hook; prepublishOnly only builds and runs unit tests.
- The MCP URL is derived from the configured HookMyApp API URL and uses its /mcp endpoint.
- MCP authentication reads the package’s saved credentials for the HookMyApp agent service; Codex setup configures that MCP endpoint.
- Telemetry is disclosed, says command arguments and file contents are not sent, and offers a disable setting.
- The scanner flags credential redirection and exfiltration, but the reviewed credential flow configures the package’s own MCP service; no unrelated credential forwarding was identified.
- The CLI can write agent configuration and install HookMyApp skills, but this is part of its agent setup flow.
Source & flagged code
9 flaggedSource appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L48A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/cli.jsFindings
Affected versions and remediation
This report applies to @gethookmyapp/cli@0.14.22.
See all versions of @gethookmyapp/cli for other recorded verdicts.
- Review the evidence and your use of @gethookmyapp/cli@0.14.22 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.