@flydocs/cli
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
This report shows the evidence for @flydocs/cli@1.3.38. 0 of 37 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged code is consistent with workflow support and disclosed anonymous analytics. I found no source evidence that credentials are sent to an unrelated host or that concealed payload behavior runs automatically.
Decision evidence
public snapshot- The manifest has no install, preinstall, or postinstall lifecycle script; its CLI entry is dist/cli.js.
- The CLI discloses anonymous usage analytics and provides status and opt-out commands.
- Analytics properties shown include CLI version, platform, architecture, Node version, and a CI flag.
- GitHub-related environment variables are added to the allowlist only for the issue.pr operation.
- The flagged repo_context.py file describes shared repository-context resolution for workflow hooks.
Source & flagged code
14 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.38.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @flydocs/cli@1.3.38 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.