@gethookmyapp/cli@0.14.27
HookMyApp CLI, No BS. Just go live.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe selectable local profile points at a fixed ngrok host, and the CLI sends login and authenticated API traffic, including access tokens, to the selected API URL. Because the package defaults to production and this requires choosing the local profile, the source supports a warning rather than a malicious verdict.
Decision evidence
public snapshot- The `local` profile sends API and app traffic to the fixed host `uninked-robbi-boughless.ngrok-free.dev`.
- Login exchanges its bootstrap code at the API URL selected by the environment, then saves the returned access token and persists that environment choice.
- Authenticated API requests send the access token as a Bearer token to the effective API URL.
- The package defaults to the production HookMyApp API; the ngrok endpoint is only in the `local` profile.
- The manifest has no install hook; its `prepublishOnly` script builds and runs tests.
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.27.
See all versions of @gethookmyapp/cli for other recorded verdicts.
- Review the evidence and your use of @gethookmyapp/cli@0.14.27 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.