@sokeai/cli@1.0.103
授客AI官方CLI工具 - 支持AI Agent Skills
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe active install path is a vendor binary downloader for this CLI, and the home-directory skill and GUI mutations are not executed. User invocation of the local binary is package-aligned and does not show a concrete attack.
Decision evidence
public snapshot- package.json exposes bin soke-cli via scripts/run.js and a postinstall hook that runs scripts/install.js, with no runtime dependencies.
- The install hook downloads the versioned soke-cli binary from the vendor CDN host, then falls back to the package GitHub Releases URL.
- Downloaded binaries are checked with sha256 against a checksum file from the same source before being saved in the package bin directory.
- Calls that would copy skills into home agent directories or run setup-gui-env sit inside a block comment; the live install path resolves without invoking them.
- scripts/run.js only spawns the already installed local binary and forwards the user's arguments.
- GitHub fallback skips checksum verification if the checksum file cannot be downloaded.
- HTTP redirects during download are followed without a host allowlist, and SOKE_CLI_BINARY_HOST can replace the default CDN.
- Dead functions would write first-party skill directories under the user home directory if the comment were removed.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @sokeai/cli@1.0.103.
See all versions of @sokeai/cli for other recorded verdicts.
- Review the evidence and your use of @sokeai/cli@1.0.103 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.