@flydocs/cli@1.2.13
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not malicious under the install-control-surface policy because there is no npm lifecycle mutation and setup is user-invoked. It remains a warning-worthy first-party agent extension due to persistent hook installation, auto-approval, and consent-gated telemetry.
Decision evidence
public snapshot- template/.claude/settings.json installs PreToolUse auto-approval and Stop/SessionStart hooks.
- template/.claude/hooks/usage-capture.py launches detached `flydocs usage report` on every Claude Stop event.
- dist/cli.js reads local Claude/Cursor session data and can POST usage records to FlyDocs.
- dist/cli.js reads Claude OAuth/Cursor tokens only to query their respective usage endpoints.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- dist/cli.js installs templates only through explicit `flydocs init`/`update` commands.
- Usage posting is gated on FlyDocs workspace consent and user opt-out controls.
- Usage records are reduced to counters/metadata; no source-code or prompt body is posted by the inspected path.
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.13.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.13 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.