cjg-skill-sync@0.3.0
CAUTIONPublisher claims: "扫描你本机已安装的技能,向藏经阁查询作者是否已发布新版本,列出变更说明并帮你安全更新。核心承诺:更新前自动备份、失败自动回滚、检测到你改过的文件绝不覆盖(先问你)、大版本升级必须你点头。默认只做"检查",不会在你不知情时改动任何文件;自动更新默认关闭,需你主动开启,开启后也只自动应用"同主版本且无本地改动"的安全更新。触发词:检查技能更新、更新技能、技能有新版本吗、升级技能、技能版本、同步技能、skill update、check skill updates、update my skills、sync skills。" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-04 and scored it 58/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: Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration. 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
What would make this Verified
22 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim j-levee: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.