@flydocs/cli@1.2.17
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource establishes explicit-user project agent configuration mutation and transcript-derived usage reporting, creating a real extension risk. It does not establish malicious behavior or an unconsented npm lifecycle attack.
Decision evidence
public snapshot- dist/cli.js init copies template .claude/.cursor hooks, commands, agents, and settings into a chosen project.
- template/.claude/settings.json registers command hooks and grants Bash permission for FlyDocs Python scripts.
- template/.claude/hooks/usage-capture.py launches `flydocs usage report` on agent Stop with a transcript path.
- dist/cli.js parses agent transcripts for usage records and posts consent-gated counters to the FlyDocs relay.
- Template scripts read FLYDOCS_API_KEY/.env credentials for authenticated FlyDocs API requests.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Agent configuration is installed only through the user-invoked `flydocs init` command.
- Hook and API behavior is package-aligned workflow, formatting, issue, and usage functionality.
- No source evidence of arbitrary remote payload execution, secret forwarding to an unrelated host, or stealth persistence.
Source & flagged code
9 flaggedSource combines credential-like environment material and outbound requests; review data flow before blocking.
Findings
Affected versions and remediation
This report applies to @flydocs/cli@1.2.17.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.2.17 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.