@flydocs/cli@1.3.14
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not concrete malicious install-time behavior because npm installation does not run the CLI. Its explicit setup and agent-extension actions still warrant a warning because they install executable hooks and remote-managed artifacts.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running flydocs init, flydocs update, or flydocs connect codex.
Impact
The selected project and optional Codex configuration gain package-controlled commands and settings.
Mechanism
Agent configuration and remote artifact installation.
AI rationale
This is not concrete malicious install-time behavior because npm installation does not run the CLI. Its explicit setup and agent-extension actions still warrant a warning because they install executable hooks and remote-managed artifacts.
Evidence
package.jsondist/cli.jstemplate/.claude/settings.jsontemplate/.claude/hooks/repo_context.py.claude/hooks.claude/settings.json.mcp.json.cursor/mcp.json.vscode/mcp.json~/.codex/config.toml
Network endpoints1
app.flydocs.ai/api/relay
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The explicit init command installs package-supplied Claude hook programs into the selected project.
- The CLI can fetch remote FlyDocs artifacts and write them beneath the selected project directory.
- The explicit Codex connection path writes a FlyDocs MCP block to the user’s Codex configuration.
Evidence against
- The manifest has no preinstall, install, or postinstall lifecycle script.
- The examined hook helper resolves local workspace paths; it does not contain an encoded payload or network code.
- Credential validation sends a supplied key to the package-aligned FlyDocs relay endpoint, not an unrelated fixed host.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
14 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 931778
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 unpkg•matchType = previous_version_dangerous_delta
matchedPackage = @flydocs/cli@1.3.13
matchedIdentity = npm:QGZseWRvY3MvY2xp:1.3.13
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg131});
L132: import { spawnSync } from "child_process";
L133: import { readFile as readFile2, realpath } from "fs/promises";
High
Findings
2 Critical10 High5 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/cli.js
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighCredential Exfiltrationdist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighEntrypoint Foreign Package Code Overwritedist/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 Dir
Affected versions and remediation
This report applies to @flydocs/cli@1.3.14.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.14 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.