commit@1.3.1
CAUTIONPublisher claims: "在 Git 仓库中分析当前变更,生成符合项目规范的 commit message,自动判断单次提交还是按功能拆分多次提交,全部提交成功后自动推送当前分支到远端;正常情况全自动不询问,命中异常规则(不能或无须提交的文件等)才请用户确认。 TRIGGER(中文):"提交一下代码""帮我 commit""这次改动提交了吧""生成 commit message 并提交""/commit""按 fix 提交" "先看看变更别提交""改一下上次的 commit"。 DO NOT TRIGGER:用户只想看变更且未表达提交意图(直接执行 git status/diff 即可); 单独的 push、pull、rebase 等远端或历史操作(无提交意图,按普通指令处理并单独确认);非 Git 仓库环境。" 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-10-28 and scored it 66/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: Access to sensitive file paths. 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
No other findings across 184 lines in 2 files.
What would make this Verified
14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim stevenwangking: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.