registry / @flydocs/cli / 1.3.1
@flydocs/cli@1.3.1
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiWarn for the explicit first-party AI-agent extension and usage-reporting surface. The source does not establish unconsented npm lifecycle execution, payload staging, credential theft, or destructive behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs `flydocs init` and then an installed Claude Stop hook fires.
Impact
Project AI-agent behavior is extended; enabled workspaces may transmit parsed usage records to FlyDocs.
Mechanism
First-party agent-hook installation with consent-gated usage reporting.
AI rationale
Warn for the explicit first-party AI-agent extension and usage-reporting surface. The source does not establish unconsented npm lifecycle execution, payload staging, credential theft, or destructive behavior.
Evidence
package.jsondist/cli.jstemplate/.claude/settings.jsontemplate/.claude/hooks/usage-capture.pytargetDir/.claude/hookstargetDir/.claude/settings.jsontargetDir/.cursor/hooks.json~/.claude/projects/*.jsonl~/.codex/sessions/*.jsonl
Network endpoints1
app.flydocs.ai/api/relay/usage/sessions
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- User-run init installs project Claude hooks and merges Claude settings.
- A Stop hook starts `flydocs usage report` with the agent transcript path.
- Reporting reads Claude/Codex/Cursor usage records and posts mapped records to FlyDocs when consent permits.
Evidence against
- package.json has no preinstall/install/postinstall lifecycle hook.
- Reporting returns without an API key, workspace ID, or enabled consent; machine and env opt-outs exist.
- No source evidence of install-time execution, remote payload loading, or credential redirection to a non-FlyDocs host.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
14 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 768082
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.2.17
matchedIdentity = npm:QGZseWRvY3MvY2xp:1.2.17
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 unpkg123});
L124: import { spawnSync } from "child_process";
L125: 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.1.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.1 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.