registry / @gethookmyapp/cli / 0.14.21
@gethookmyapp/cli@0.14.21
HookMyApp CLI, No BS. Just go live.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential and endpoint behavior resolves to HookMyApp’s own MCP API, while the ngrok URL appears only in the local development profile. Runtime crash and usage telemetry is disclosed, including its account identifiers, and can be disabled.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Telemetry initializes when the CLI starts; MCP credentials are used when its MCP header helper runs.
Impact
No malicious credential redirection, unrelated collection, or unrequested account action was identified.
Mechanism
Crash reports go to the configured Sentry service and may include account email and user ID. MCP bearer tokens are directed to the HookMyApp API endpoint.
AI rationale
The flagged credential and endpoint behavior resolves to HookMyApp’s own MCP API, while the ngrok URL appears only in the local development profile. Runtime crash and usage telemetry is disclosed, including its account identifiers, and can be disabled.
Evidence
HookMyApp config directory (telemetry settings and Sentry offline queue)~/.codex/config.toml~/.cursor/mcp.json
Network endpoints3
o4511121201627136.ingest.de.sentry.ioapi.hookmyapp.comuninked-robbi-boughless.ngrok-free.dev
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the CLI and has only a prepublishOnly build/test hook; it declares no install, preinstall, or postinstall hook.
- The CLI entrypoint imports dist/cli.js when the command is run.
- The ngrok endpoint is in the local development profile; the production profile uses api.hookmyapp.com.
- Telemetry is disclosed on first run, including that logged-in email and user ID accompany crash reports, and users can disable it with a config setting or environment variable.
- The MCP header helper uses the HookMyApp API URL and sends a HookMyApp access token as a bearer credential.
Evidence against
- Crash reporting includes account email and user ID, but the package discloses this and provides a telemetry opt-out.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/cli.jsView file
48* Constructs the CommanderError class
L49: * @param {number} exitCode suggested exit code which could be used with process.exit
L50: * @param {string} code an id string representing the error
...
L1204: var EventEmitter = __require("node:events").EventEmitter;
L1205: var childProcess4 = __require("node:child_process");
L1206: var path3 = __require("node:path");
...
L1254: this._outputConfiguration = {
L1255: writeOut: (str) => process19.stdout.write(str),
L1256: writeErr: (str) => process19.stderr.write(str),
...
L1296: * @returns {Command[]}
L1297: * @private
L1298: */
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L4848Trigger-reachable chain: manifest.bin -> bin/hookmyapp.js -> dist/cli.js
L48: * Constructs the CommanderError class
L49: * @param {number} exitCode suggested exit code which could be used with process.exit
L50: * @param {string} code an id string representing the error
...
L1204: var EventEmitter = __require("node:events").EventEmitter;
L1205: var childProcess4 = __require("node:child_process");
L1206: var path3 = __require("node:path");
...
L1254: this._outputConfiguration = {
L1255: writeOut: (str) => process19.stdout.write(str),
L1256: writeErr: (str) => process19.stderr.write(str),
...
L1296: * @returns {Command[]}
L1297: * @private
L1298: */
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/cli.jsFindings
2 Critical6 High3 Medium5 Low
CriticalCredential Exfiltrationdist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighTrigger Reachable Credential Exfiltrationdist/cli.js
HighSemantic Analysis Limiteddist/cli.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @gethookmyapp/cli@0.14.21.
See all versions of @gethookmyapp/cli for other recorded verdicts.
- Review the evidence and your use of @gethookmyapp/cli@0.14.21 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.