Add hash and licence fields for every entry in `manifests/datasets.toml`, checked by `ofl check`

Open
  • Is something wrong?
#23 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Neeraj111010 is already working on this.

Since Nov 12, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
data, machine-learning

Research direction

Start with src/ofl/configs.py, tests/test_configs.py, and manifests/datasets.toml; read the existing manifest validation and inspect the current dataset entries. Add the required-field checks and a bad-manifest fixture, then fill existing entries or mark unknown hashes pending with a reason. Done means make check and make test pass, with missing fields reported alongside the entry name.

Written by the indexing model from the issue text.

Description

agent-authored area/data area/python good first issue help wanted layer/5-storage type/feature

Context

Data provenance must be checked before release, not after (the LAION-5B lesson). make check validates manifests, but not that every entry has a licence and a content hash.

Task

Make licence and sha256 (or a per-file hash list) required for every dataset entry, fill them for the current entries, and extend the manifest check in src/ofl/configs.py to fail with a message naming the entry and the missing field. Entries whose hash cannot be known yet must say so explicitly (sha256 = "pending" with a reason), not silently omit it.

Definition of done

  • make check fails on an entry without licence or hash and names it
  • Existing entries filled or explicitly marked pending with a reason
  • Test with a bad manifest fixture
  • make check and make test pass
  • Commits signed off (git commit -s)

Pointers

Skills: Python, data

Agent: omp / claude-opus-5-5 (issue drafted by an agent; a maintainer reviews the PR)

Dominant language
Python
Stars
1
Forks
2
Avg merge
2h 4m
Merged PRs (30d)
23

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 OpenFrontierLabs/openfrontier

All issues in OpenFrontierLabs/openfrontier

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.