Make deterministic (non-LLM) audits explicitly test-only
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
Start by reading the darnit audit and darnit run command entry points, then trace how run headers, machine-readable output, and compliance levels are produced. Review the README and install/usage docs for the relevant descriptions. Done means deterministic runs are clearly marked as test-only, make no compliance claims or attestations, keep judgment-dependent controls pending, and the help and docs point users to the supported surfaces.
由索引模型根据 Issue 内容生成。
描述
Summary
The deterministic (non-LLM) audit paths -- darnit audit, darnit run, and any mode that runs controls without resolving LLM judgments -- exist to test individual handlers, passes, and controls during development. They are not a supported way to evaluate a project. The supported surfaces are the MCP server with agent skills (a coding agent answers the judgment tasks) and darnit harness (the headless driver for CI and fleets, which dispatches LLM judgments itself).
Today nothing in the output or documentation makes that distinction, so a deterministic run can look like a real compliance result.
Proposed changes
- Label the output. Deterministic runs state in their header and in machine-readable output (
run_mode: "deterministic-test") that they are a development/test run and not a compliance result. Controls that would need a judgment remain pending and are shown as such. - No compliance claims. Deterministic runs do not report a level as compliant and do not produce attestations, in line with conservative-by-default.
- Help and docs. CLI help for these commands, the README, and the install/usage docs describe them as testing tools and point users to the MCP server + skills or
darnit harness. - Focused test tooling (optional). Consider a narrower entry point for the actual use case -- running one control or one handler against a fixture repository and printing each pass's outcome and evidence -- so plugin authors have a first-class way to test hooks.
Out of scope
Removing the deterministic engine: the check engine itself is shared by every driver, and deterministic passes remain the first step of every real run.
- 主要语言
- Python
- 星标
- 22
- 派生
- 27
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 51
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
darnitdevorg/darnit 的其他 Issue
-
module-core needs triage ux
难度 2/5 1-3 小时 新手友好度 72/100
darnitdevorg/darnit#648 ·
维护者通常 2 天内回复
-
ci needs triage
难度 2/5 1-3 小时 新手友好度 62/100
darnitdevorg/darnit#607 ·
维护者通常 2 天内回复
-
attestation extra allows sigstore 3.x, but signing needs sigstore 4.0可能已有人在做 @JohnsonLyu 于 2 天前认领。 未关闭dependencies module-baseline needs triage
难度 2/5 1-3 小时 新手友好度 68/100
darnitdevorg/darnit#606 ·
维护者通常 2 天内回复
-
`darnit validate` crashes on openssf-baseline.toml summarising levels可能已有人在做 @i-am-paradox 于 14 天前认领。 未关闭interface-cli module-core
难度 2/5 1-3 小时 新手友好度 78/100
darnitdevorg/darnit#589 · 1 条评论 ·
维护者通常 2 天内回复
-
good first issue maintenance
难度 2/5 1-3 小时 新手友好度 83/100
darnitdevorg/darnit#587 · 2 条评论 ·
维护者通常 2 天内回复
查看 darnitdevorg/darnit 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 72/100
521xueweihan/HelloGitHub#4150 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
aws-samples/sample-per-model-bedrock#595 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
bug connectors
难度 1/5 1 小时以内 新手友好度 67/100
pyinfra-dev/pyinfra#2036 ·
维护者通常 9 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复