@flydocs/cli@1.2.16
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a real first-party AI-agent extension lifecycle surface, but source shows explicit user triggering, no npm lifecycle mutation, and consent-gated reporting rather than a concrete malicious chain.
Decision evidence
public snapshot- User-invoked init/update writes bundled Claude/Cursor hooks and settings.
- template/.claude/hooks/usage-capture.py starts detached usage reporting on agent Stop.
- dist/cli.js reads local Claude/Cursor auth state for plan/usage queries.
- Template hook post-edit.py may invoke npx prettier on edited projects.
- package.json has no preinstall/install/postinstall lifecycle hook.
- Agent configuration is installed only through explicit CLI commands.
- Usage reporting denies by default without credentials, workspace consent, and opt-out checks.
- Observed endpoints are FlyDocs telemetry/relay and provider usage APIs; no arbitrary payload URL.
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.16.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.16 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.