@flydocs/cli@1.2.14
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package is not concretely malicious, but it installs first-party agent hooks that automatically collect and upload AI usage metadata after workspace consent. This warrants a warning under the agent-extension lifecycle policy.
Decision evidence
public snapshot- template/.claude/settings.json installs Stop hooks after explicit CLI setup.
- usage-capture.py launches `flydocs usage report` on each agent Stop event.
- dist/cli.js reads local Claude/Codex/Cursor session records and can POST usage data.
- dist/cli.js reads Claude OAuth credentials solely to query Anthropic usage status.
- package.json has no preinstall, install, or postinstall hook.
- Usage upload is gated by workspace consent, API credentials, and a machine opt-out.
- Wire records contain usage counters/metadata; inspected serializer does not include transcript text.
- Agent files are project-local FlyDocs templates, not install-time broad host mutation.
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.14.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.14 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.