@flydocs/cli@1.3.9
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source establishes user-command agent configuration mutation, including a configurable global permission destination. No install lifecycle trigger or concrete malicious attack was established, so the supplied policy requires a warning rather than blocking publication.
Decision evidence
public snapshot- The explicit update command replaces project Claude hooks and writes managed agent permissions.
- Update reads the saved permission policy; its destination can be project or user-global Claude settings.
- The CLI exposes update as a user-invoked command, and package.json has no npm install lifecycle hooks.
- The indicated directory helper creates agent skill and command directories.
- The Python helper maintains local repository session state.
- No concrete malware attack was established by the inspected source.
- Permission writes preserve a backup of existing settings and support an off mode.
Source & flagged code
13 flaggedA 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 unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @flydocs/cli@1.3.9.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.9 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.