Nothing checks that each audit's dataset source link agrees between the README and the scripts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Read README.md and the header comments in each audit’s unfair.py and fair.py to see how source URLs are recorded; the issue cites #1175 as an example of a mismatch. Add a check that compares each README block’s URL with both script comments and reports disagreements. It is done when the check fails after a URL is changed in one place and passes on the current files.
Written by the indexing model from the issue text.
Description
Where: README.md, each audit's unfair.py and fair.py.
Current gap: The Kaggle address of a dataset is written in the README and again in the header comment of two scripts per audit (for example ppb00x/credit-risk-customers), and the NIJ link in #1175 went dead in one place only.
Suggested approach: Add a check that the source URL in each audit's README block equals the URL in its script comments and report disagreements.
Done when: the check fails when one place changes and passes on the current files.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 10m
- Merged PRs (30d)
- 100
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/Fair-Code
-
The benchmark OG card and the home card hard-code counts and domains that are also kept elsewhereOpenenhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yakew7/Fair-Code#1198 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement help wanted tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
yakew7/Fair-Code#1169 · 1 comment ·
Maintainers usually reply within 1 day
-
ci enhancement testing
Difficulty 3/5 1-2 days Newbie friendliness 72/100
yakew7/Fair-Code#1209 · 1 comment ·
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
fix(worker): keep normal prepare waiting states failure-freePossibly taken @LichKing-2234 claimed this today. Openagent:codex priority:P1
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AgoraIO-Extensions/agent-infra#3745 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oracle/graalvm-reachability-metadata#11472 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
FireDynamics/LEDSmokeAnalysis#176 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/senpi#4917 · 1 comment ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Aethelgard-Systems/agent-postbox#32 ·
Maintainers usually reply within 1 day