@flydocs/cli@1.3.13
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an explicit user-command agent configuration tool with credentialed network behavior and remote artifact writes. It should be warned as a dangerous capability, not blocked as malware, because no npm install hook or concrete malicious behavior was found.
Decision evidence
public snapshot- The user-invoked initializer creates Claude and Cursor agent directories in the target project.
- The bundled Claude settings pre-approve FlyDocs commands and register hooks that run project-local Python.
- A session-start hook reads a FlyDocs API key and sends it as a bearer token to the FlyDocs relay.
- Cloud artifact sync writes server-provided content into the project after path validation.
- The manifest has no preinstall, install, or postinstall lifecycle hook; the executable is a user-run CLI.
- The credential request uses the FlyDocs relay endpoint named by the product and is limited to configured cloud projects.
- Artifact writes reject protected paths and resolve paths under the selected project root.
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 unpkgFindings
Affected versions and remediation
This report applies to @flydocs/cli@1.3.13.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.13 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.