@flydocs/cli@1.3.16
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an explicit-user-command agent configuration mutation with persistent hooks and session telemetry. It warrants a warning, not a block, because there is no install lifecycle hook and reporting is consent-gated.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs flydocs init, then uses a configured Claude project.
Impact
Persistent project hooks can collect session metadata and send it to the FlyDocs relay; the source gates reporting on consent and offers opt-out.
Mechanism
Project agent-hook installation and usage reporting.
AI rationale
This is an explicit-user-command agent configuration mutation with persistent hooks and session telemetry. It warrants a warning, not a block, because there is no install lifecycle hook and reporting is consent-gated.
Evidence
dist/cli.jstemplate/.claude/settings.jsontemplate/.claude/hooks/usage-capture.py.claude/settings.json.claude/hooks/usage-capture.py.codex/sessions
Network endpoints1
app.flydocs.ai/api/relay/usage/sessions
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The explicit init command installs project Claude hooks and settings.
- The installed settings run Python commands on Claude tool and stop events.
- The stop hook starts a detached usage-report process with the agent transcript path.
- The report reads Claude, Codex, and Cursor session records and posts usage batches to FlyDocs.
- This creates persistent agent-side collection after user-invoked setup.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The report checks an opt-out and a workspace consent flag before reading transcripts.
- No source evidence shows hidden install-time execution, self-dependency, or secret theft.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
12 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 935555
triggerReachableSource = dist/cli.js
excludedPayload = template/.claude/hooks/auto-approve.py
Critical
Trigger Reachable Excluded Directory Payload
A 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 unpkg131});
L132: import { spawnSync } from "child_process";
L133: import { readFile as readFile2, realpath } from "fs/promises";
High
122SKIP_VERSION_CHECK_ENV: () => SKIP_VERSION_CHECK_ENV,
L123: buildReExecArgv: () => buildReExecArgv,
L124: closestCommand: () => closestCommand,
High
Findings
1 Critical9 High5 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighCredential Exfiltrationdist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighTrigger Reachable Credential Exfiltrationdist/cli.js
HighRuntime Package Installdist/cli.js
HighPayload In Excluded Dirtemplate/.claude/hooks/repo_context.py
MediumDynamic Requiredist/cli.js
MediumNetwork
Affected versions and remediation
This report applies to @flydocs/cli@1.3.16.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.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.