@flydocs/cli@1.3.2
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not malicious by the stated boundary because setup is CLI-triggered rather than an npm lifecycle action and credential use is package-aligned. It warrants a warning because it deploys persistent AI-agent hooks/permissions and accesses local agent credentials.
Decision evidence
public snapshot- Interactive CLI invocation without a command defaults to init.
- The shipped template owns and overwrites Claude settings and hook directories.
- Template enables a FlyDocs MCP server and command hooks, including a Stop usage-capture hook.
- Usage code reads Claude OAuth credentials and calls Anthropic's usage endpoint only when plan status is allowed.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The package is activated through its flydocs bin, not on npm installation.
- Credential use targets the official Anthropic API; no source evidence shows token forwarding to FlyDocs or another host.
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.2.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.2 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.