@flydocs/cli@1.3.35
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThis is suspicious runtime telemetry rather than credential theft: reporting is workspace-gated and has an opt-out, but its records can include repository and session identifiers beyond the stated notice. The manifest has no install lifecycle hook, and the Claude OAuth token is used with Anthropic’s own usage endpoint.
Decision evidence
public snapshot- A Stop hook launches usage reporting, which posts records to the FlyDocs relay; reporting is gated by the workspace’s server-side analytics setting.
- The records can include session IDs, repository slugs and host data, while the notice describes collection as token counts and estimated cost only.
- package.json defines no install, preinstall or postinstall lifecycle script.
- Usage reporting is gated by workspace consent and supports a local opt-out.
- The Claude OAuth token is used for an Anthropic usage request to api.anthropic.com, its own service.
Source & flagged code
13 flaggedA package entrypoint or install-reachable source explicitly loads and activates an executable-looking payload from a test, fixture, or hidden path.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @flydocs/cli@1.3.35.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.35 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.