Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Outputs disagree on Baseline version and assessor identity (2025.10.10 vs v2026.02.19, nonexistent baseline-mcp)

未关闭
#494 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

@i-am-paradox 已经在做这个了。

开始于 2026年10月14日。

  • #603 来自 @i-am-paradox —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
tooling

调研方向

Start with openssf-baseline.toml and trace the version and tool identity through attestation/predicate.py, formatters/sarif.py, and attestation/signing.py; check the related tests for expected output. Done means outputs use consistent version and identity values, and references to the nonexistent baseline-mcp package are removed.

由索引模型根据 Issue 内容生成。

描述

good first issue module-baseline quality

Summary

darnit's outputs disagree about which OSPS Baseline version was assessed and who the assessor is:

  • Framework TOML metadata: spec_version = "OSPS v2026.02.19"
  • Attestation predicate: hard-codes baseline 2025.10.10 and an assessor named openssf-baseline-mcp with a URI for a repository that does not exist
  • SARIF formatter and about 60 control docs_url values: link to baseline.openssf.org/versions/2025-10-10
  • Attestation install hints reference a baseline-mcp package that does not exist

Impact

A signed attestation that names the wrong spec version and a nonexistent assessor is misleading to consumers, and version-specific control text links point at an older Baseline release than the one the controls were synced to.

Evidence

Suggested direction

Derive the spec version and tool identity from one place (TOML [metadata] and the installed package version) in every output; drop the hard-coded values and the baseline-mcp references. Separately, the predicate type lives under the openssf.org namespace, which darnit does not own; that is being discussed as part of the output-format review.

主要语言
Python
星标
22
派生
27
平均合并
2 天 19 小时
30 天内合并 PR
51

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

darnitdevorg/darnit 的其他 Issue

查看 darnitdevorg/darnit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。