@flydocs/cli@1.3.12
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a real conditional credential-exposure capability, not an automatic install-time attack. The default service is package-aligned, but the unrestricted endpoint override and credential-bearing agent settings write warrant a warning.
Decision evidence
public snapshot- The package has no npm install lifecycle hook; its executable is the user-invoked CLI.
- The CLI loads a FlyDocs API key from an environment variable or local credential files.
- A relay URL environment variable can replace the default endpoint, and the API key is sent as a Bearer credential.
- Server-supplied OTel settings substitute that API key into a header and can target the user-global Claude settings file.
- The init flow pulls configuration from the server and later applies the managed OTel block.
- The default relay host is app.flydocs.ai, which is aligned with the package name.
- The credential forwarding and settings mutation require CLI runtime activity rather than occurring at package installation.
Source & flagged code
13 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 unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @flydocs/cli@1.3.12.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.12 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.