wechat-use@0.1.0
CAUTION· static onlyPublisher claims: "macOS WeChat CLI + local HTTP bridge + Wechaty Puppet gRPC gateway — send messages, query sessions / contacts / chat history / images / favorites, and expose..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-12 and scored it 53/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Direct script execution from GitHub raw URL; Direct script execution from GitHub raw URL; Pipe-to-shell pattern. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh | bashFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Resolver 优先级:wxid-shape > **alias** > contact.db fuzzy。`wechat-use send` /Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh | bashFix: Pin versions and sources; vendor anything fetched at install time.npx skills update leeguooooo/wechat-use -gFix: Pin versions and sources; vendor anything fetched at install time.curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh | bashFix: Pin versions and sources; vendor anything fetched at install time.If the agent sees `wechat: command not found` after an `npx skills update`, it still needs to run `install.sh` — skill updates do **not** include the binary.Fix: Pin versions and sources; vendor anything fetched at install time.curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh | bashFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh | bashFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…-spawned wechatd with a stale launchd responsibility chain | Re-run `curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh \| bash`. v1.16.12+ install.sh bootouts every `ai.wechat.*.plist` and bootstrap…Fix: Pin versions and sources; vendor anything fetched at install time.…epAlive) re-spawned wechatd with a stale launchd responsibility chain | Re-run `curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh \| bash`. v1.16.12+ install.sh bootouts every `ai.wechat.*.plist` and bootst…Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…epAlive) re-spawned wechatd with a stale launchd responsibility chain | Re-run `curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh \| bash`. v1.16.12+ install.sh bootouts every `ai.wechat.*.plist` and bootst…Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -fsSL https://raw.githubusercontent.com/leeguooooo/wechat-use/main/install.sh | bashFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
27 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim leeguooooo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Direct script execution from GitHub raw URL≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.