获批评估会执行未预先限定的夹具命令和仓库检查
原文依据:3 处技能要求记录并运行“确切命令”,还会执行仓库的 focused code checks,但没有限定允许的命令、网络访问或进程权限。如果仓库或测试脚本不可信,这些命令可能执行任意项目代码。
恶意或被篡改的脚本可能读取当前进程可见的凭据、访问网络、修改工作区文件,或调用本机工具。操作员批准评估设计能降低风险,但不会自动证明其中命令安全。
这里的命令执行属于经操作者明确批准的评估流程:技能要求先提出包含确切夹具和命令的方案并获得批准,然后才编辑和运行配对评估。仓库检查确实可能执行项目代码,但原文没有要求执行隐藏、任意或未经批准的命令。用户仍应在批准时确认命令及其网络和进程权限。
这项判断针对展示的代码和适用条件,不表示风险已经实际发生。Propose one minimal candidate change and a **paired eval** before editing. Theevaluation must run baseline and candidate on identical fixed inputs and record:- the task-outcome or quality check that must remain acceptable;- the same token, byte, or provider-counted cost measure for both arms;- the exact fixture, command, and environment used; and- any confounder that prevents a fair comparison.查看另外 2 个位置
Keep the diff at the evidenced callsite and preserve existing safety controls.Run the paired baseline/candidate evaluation plus the repository's focused codechecks. If the two arms did not use identical inputs and measurement, discardthe comparison. If quality regresses or the resource result is inconclusive,Ask for approval of the candidate and eval design. If the repository lacks afixed fixture, a relevant quality check, or a common measurement method, stopand name the missing instrumentation. Ordinary unit tests alone do not prove anoptimization.