@sokeai/cli@1.0.88
授客AI官方CLI工具 - 支持AI Agent Skills
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a real remote-payload supply-chain surface, but the inspected JavaScript does not prove malicious payload behavior, credential theft, broad agent-control mutation, or a self-dependency lifecycle chain. It should be warned pending a review of the published binary and release integrity.
Decision evidence
public snapshot- The automatic postinstall hook downloads a platform-specific executable from the network.
- The download source can be overridden through an environment variable and redirects are followed without host restrictions.
- The downloaded file is placed in bin/soke-cli and the command wrapper later executes it.
- Checksum verification retrieves the checksum from the same selected remote source, so it does not provide an independent trust boundary.
- No runtime dependency on another release of this package is declared.
- The source does not harvest credentials or send local data to a remote endpoint.
- The install-time code that would copy skills into agent workspaces and modify a registry is commented out.
- The downloaded executable is not launched by postinstall; it runs when the user invokes the CLI.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
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.88.
See all versions of @sokeai/cli for other recorded verdicts.
- Review the evidence and your use of @sokeai/cli@1.0.88 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.