registry / @flydocs/cli / 1.3.27
@flydocs/cli@1.3.27
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
AI Security Review
scanned 22d ago · by lpm-firewall-aiThere is no npm install lifecycle hook, and the agent configuration is installed through the CLI project setup flow. Because that setup adds event hooks and scoped automatic approvals, classify this as a guarded agent integration risk and warn.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI project setup or update flow.
Impact
Claude project behavior changes, and matching FlyDocs workflow scripts can run without individual approval.
Mechanism
The CLI creates agent directories, copies hook scripts, and installs settings that attach those scripts to Claude events.
AI rationale
There is no npm install lifecycle hook, and the agent configuration is installed through the CLI project setup flow. Because that setup adds event hooks and scoped automatic approvals, classify this as a guarded agent integration risk and warn.
Evidence
dist/cli.jstemplate/.claude/settings.jsontemplate/.claude/hooks/auto-approve.pytemplate/.claude/hooks/session-start.py
Network endpoints1
app.flydocs.ai/api/relay
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json exposes the CLI entrypoint and defines no install lifecycle script.
- The CLI setup creates agent directories, installs package hooks, and copies managed settings into the project.
- Claude settings register tool and session hooks; the approval hook allows only commands matching the FlyDocs workflow script pattern.
- The flagged Python helper resolves repository and session paths from local workspace state.
- The session-start hook sends a FlyDocs API key to the config-check route, defaulting to the FlyDocs relay.
Evidence against
- The agent setup is reached through the CLI project setup flow, not an npm install hook.
- The approval hook is scoped to FlyDocs workflow scripts, and the inspected credential request defaults to the FlyDocs relay.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
Source & flagged code
13 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 1103756
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 unpkg137});
L138: import { spawnSync } from "child_process";
L139: import { readFile as readFile2, realpath } from "fs/promises";
High
128SKIP_VERSION_CHECK_ENV: () => SKIP_VERSION_CHECK_ENV,
L129: buildReExecArgv: () => buildReExecArgv,
L130: closestCommand: () => closestCommand,
High
Findings
1 Critical10 High5 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighSame File Env Network Executiondist/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
Affected versions and remediation
This report applies to @flydocs/cli@1.3.27.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.27 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.