@flydocs/cli@1.3.3
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource confirms an explicit-user-command, first-party AI-agent extension setup with persistent hooks and usage reporting. No install-time lifecycle execution, credential theft, remote payload execution, or broad foreign control-surface mutation was found.
Decision evidence
public snapshot- Explicit `flydocs init` installs FlyDocs settings and Cursor hooks into the target project.
- Installed Claude settings grant FlyDocs MCP/Bash permissions and register command hooks.
- A Stop hook launches detached usage reporting against agent transcript input.
- CLI usage reporting is consent-gated before parsing and posting records.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- Agent configuration changes occur through the explicit `flydocs init` command, not npm installation.
- Permissions and endpoints are FlyDocs-scoped; no obfuscated payload, arbitrary shell execution, or credential diversion was found.
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.3.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.3 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.