@flydocs/cli@1.2.11
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is an explicit-user-command, first-party agent extension with detached hook execution and sensitive local telemetry access. It warrants warning for lifecycle/privacy risk, but source inspection does not establish malicious behavior.
Decision evidence
public snapshot- Explicit CLI setup installs Claude/Cursor hooks and agent files into the target project.
- Stop hook launches detached `flydocs usage report` after agent responses.
- Usage reporting reads local Claude, Codex, and Cursor session metadata; it posts records to FlyDocs only after workspace consent checks.
- Plan probes read Claude/Cursor auth tokens to query their respective provider usage APIs.
- package.json has no npm lifecycle hooks.
- Agent files are installed by user-invoked CLI init/update paths, not at package installation.
- Provider tokens are used for provider usage endpoints; no source path sends those tokens to FlyDocs.
- No destructive or covert install-time behavior 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.11.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.11 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.