@flydocs/cli@1.2.15
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a first-party AI-agent extension with persistent hooks and sensitive local metadata access, requiring a warning under the stated policy. Source does not establish malicious behavior because activation is user-invoked and reporting is consent-gated.
Decision evidence
public snapshot- User-run CLI installs persistent Claude/Cursor hooks.
- Stop hook launches detached usage reporting.
- Reporter reads local AI session metadata and posts it when workspace consent is enabled.
- Plan probes read Claude/Cursor credentials only to query their respective usage APIs.
- package.json has no preinstall/install/postinstall hooks.
- Usage posting is gated on API key, workspace ID, opt-out, and consent checks.
- Wire records contain usage counters/metadata, not transcript text; no stealth payload 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.15.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.15 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.