METRICS.md's own badge says 61 explainers; its own Targets table says 56 two sections later
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
The issue points to METRICS.md lines 9 and 107. First, verify the current explainer count by running ls explainers/*.md | wc -l. Then, update the 'Current' cell in the Targets table from 56 to 61. Also, consider updating the '60+' target. Finally, edit scripts/check_explainer_count.py to add the Targets table line to the CHECKS list to prevent future drift.
Written by the indexing model from the issue text.
Description
Where: METRICS.md line 9 (badge) vs. line 107 (Targets table).
The gap:
Line 9: 
Line 107: | Explainers | 56 | 60+ | End of 2026 |
The badge and the Targets table's "Current" column are both meant to state today's live explainer count, and they disagree within the same file. The real count is 61:
$ ls explainers/*.md | wc -l
61
scripts/check_explainer_count.py (which CI runs) doesn't catch this - its CHECKS list only tracks 6 specific regexes (README's "Show all N explainers", "Explainers Published | N", "N short, plain-language write-ups"; CONTRIBUTORS.md's "the bulk of the N explainers"; METRICS.md's Explainers-N-blueviolet badge itself; and ROADMAP.md's "N explainers published") - the Targets table's own "Explainers" row isn't in that list, so it drifted silently. Also worth noting: the real count (61) already exceeds the Targets table's own "60+" target.
Repro:
$ python3 scripts/check_explainer_count.py
OK: all 6 explainer-count mentions match explainers/*.md (61 files).
Passes cleanly even though this 7th, untracked mention is stale.
Fix direction: Update the Targets table's Explainers "Current" cell from 56 to 61 (and reconsider the "60+" target, already exceeded), and add this line to check_explainer_count.py's CHECKS list so it can't drift silently again.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 97
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
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
yakew7/Fair-Code#731 · 2 comments ·
Maintainers usually reply within 1 day
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
inu-appcenter/memorIN-frontend#106 ·
Maintainers usually reply within 1 day
-
workflow: a tick's dispatch counts as 'only this step', and no review self-grants a round unattendedOpenworkflow
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
kristofdegrave/homeassistant-smart-charging#1505 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openfoodfacts/score-my-recipe#80 ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#3968 ·
Maintainers usually reply within 1 day