@flydocs/cli@1.3.22
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package creates a user-invoked AI-agent hook and reporting path with a remote telemetry endpoint. Its absence of npm lifecycle execution and its code-enforced opt-out and consent checks make a block unwarranted.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs FlyDocs setup and then ends a Claude Code response in that configured project.
Impact
AI session metadata and derived usage records may leave the machine through the FlyDocs relay.
Mechanism
Project AI-agent hook installation followed by consent-gated transcript-derived usage reporting.
AI rationale
The package creates a user-invoked AI-agent hook and reporting path with a remote telemetry endpoint. Its absence of npm lifecycle execution and its code-enforced opt-out and consent checks make a block unwarranted.
Evidence
dist/cli.jstemplate/.claude/hooks/usage-capture.py.claude/hooks.claude/hooks/usage-capture.py.claude/settings.json
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 setup flow replaces project Claude hook files.
- The installed Stop hook starts a detached usage-report command after agent responses.
- The report command reads AI transcripts and posts derived records to the FlyDocs relay.
Evidence against
- The manifest has no preinstall, install, or postinstall lifecycle hook.
- Reporting stops without credentials or enabled usage consent, and supports machine and environment opt-out.
- The flagged repo_context hook is ordinary local workspace-path handling, not a hidden payload.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 954452
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.22.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.22 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.