Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#494 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
22
Forks
27
Avg merge
1d 20h
Merged PRs (30d)
39

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from darnitdevorg/darnit

All issues in darnitdevorg/darnit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.