@flydocs/cli@1.3.23
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe unrestricted credential forwarding path is a real dangerous capability under the credential-forwarding policy. No evidence supports blocking as malware or install-hook abuse.
Decision evidence
public snapshot- The CLI accepts an API key interactively and validates it.
- The relay base URL is controlled by FLYDOCS_RELAY_URL without destination allowlisting, and the API key is sent as a Bearer token to that URL.
- Usage records are posted to the same configurable relay URL with the API-key authorization header.
- The manifest has no npm preinstall, install, or postinstall hook.
- The Claude hook is deployed only by the explicit init command; it is not an install-time payload.
Source & flagged code
12 flaggedA package entrypoint or install-reachable source explicitly loads and activates an executable-looking payload from a test, fixture, or hidden path.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @flydocs/cli@1.3.23.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.23 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.