@flydocs/cli@1.2.12
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo install-time execution or concealed malware chain was found. The package nevertheless deploys persistent AI-agent hooks and reads local AI-session/credential-adjacent data after explicit setup, so it warrants a non-blocking warning.
Decision evidence
public snapshot- `template/.claude/settings.json` installs Stop hooks into Claude projects.
- `usage-capture.py` detaches `flydocs usage report` on every agent Stop event.
- `dist/cli.js` reads in-scope Claude/Codex/Cursor session data and posts usage records to FlyDocs.
- `dist/cli.js` reads Claude OAuth credentials to query Anthropic plan usage.
- `package.json` has no preinstall/install/postinstall lifecycle hook.
- Agent files are written only by the user-invoked `flydocs init`/update flow.
- Usage reporting requires FlyDocs credentials and a consent decision; machine opt-out is supported.
- Observed endpoints are declared FlyDocs, PostHog, Anthropic, and provider APIs; no hidden payload fetch found.
Source & flagged code
9 flaggedSource combines credential-like environment material and outbound requests; review data flow before blocking.
Findings
Affected versions and remediation
This report applies to @flydocs/cli@1.2.12.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.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.