registry / @flydocs/cli / 1.3.26
@flydocs/cli@1.3.26
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe suspicious scanner signals did not establish malicious behavior in the inspected source. The package exposes a user-invoked CLI without install hooks, and the flagged agent-related code is ordinary project setup and workspace reading.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI runs when a user invokes it; the manifest defines no install lifecycle hook.
Impact
No harmful effect was established from the inspected source.
Mechanism
The flagged agent-related code creates project directories, while the Python helper reads workspace configuration.
AI rationale
The suspicious scanner signals did not establish malicious behavior in the inspected source. The package exposes a user-invoked CLI without install hooks, and the flagged agent-related code is ordinary project setup and workspace reading.
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entrypoint and has no install lifecycle hooks.
- The flagged CLI location creates project directories for FlyDocs and editor integrations; it does not execute or install agent code.
- The flagged Python hook helper reads workspace configuration from the current directory.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 1072955
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 unpkg134});
L135: import { spawnSync } from "child_process";
L136: import { readFile as readFile2, realpath } from "fs/promises";
High
125SKIP_VERSION_CHECK_ENV: () => SKIP_VERSION_CHECK_ENV,
L126: buildReExecArgv: () => buildReExecArgv,
L127: 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.26.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.26 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.