tuniu-cli@1.0.5
CAUTION· static onlyPublisher claims: "途牛旅行统一助手(推荐优先使用)- 通过 tuniu CLI 统一调用机票、酒店、门票、火车票、邮轮、度假产品等旅行服务。适用于用户询问航班、酒店、景点门票、火车票、邮轮以及跟团游、自助游、自驾游等度假相关需求的场景。【优先级说明】当同时安装了 tuniu-flight/tuniu-hotel/tuniu-tic..." 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-13 and scored it 61/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
npx tuniu-cli --versionFix: Pin versions and sources; vendor anything fetched at install time.npx tuniu-cli --versionFix: Pin versions and sources; vendor anything fetched at install time.# 或使用 npx 临时调用Fix: Pin versions and sources; vendor anything fetched at install time.# 或使用 npx 临时调用Fix: Pin versions and sources; vendor anything fetched at install time.4. **配置文件仅作兜底**:若无法设置环境变量,且用户明确同意把密钥写入本地文件,可初始化 `~/.tuniu-mcp/config.json` 并把各服务 `headers.apiKey` 从 `${TUNIU_API_KEY}` 改为实际密钥,同时将文件权限设为仅当前用户可读写(例如 `chmod 600 ~/.tuniu-mcp/config.json`)。Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.4. **配置文件仅作兜底**:若无法设置环境变量,且用户明确同意把密钥写入本地文件,可初始化 `~/.tuniu-mcp/config.json` 并把各服务 `headers.apiKey` 从 `${TUNIU_API_KEY}` 改为实际密钥,同时将文件权限设为仅当前用户可读写(例如 `chmod 600 ~/.tuniu-mcp/config.json`)。Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.npm install -g tuniu-cli@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.- 若 `tuniu` 不存在,但 Node.js 版本满足要求,自动执行 `npm install -g tuniu-cli@latest`安装 CLI。Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.- 若 `node` 不存在,或版本低于 18:不要继续安装 `tuniu-cli`;告知用户需先安装或升级 Node.js 18+,否则 `npm install -g tuniu-cli@latest` 会失败。Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.- 若 `node` 不存在,或版本低于 18:不要继续安装 `tuniu-cli`;告知用户需先安装或升级 Node.js 18+,否则 `npm install -g tuniu-cli@latest` 会失败。Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.1. 若 `tuniu --version` 低于 `minCliVersion`,先执行 `npm install -g tuniu-cli@latest` 更新 CLI。Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.1. 若 `tuniu --version` 低于 `minCliVersion`,先执行 `npm install -g tuniu-cli@latest` 更新 CLI。Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.- 若 `tuniu` 不存在,但 Node.js 版本满足要求,自动执行 `npm install -g tuniu-cli@latest`安装 CLI。Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.npm install -g tuniu-cli@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.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
19 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim leonardoooooo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Unpinned dependencies≈ +4 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.