49
/ 100
Lots of room to improve. Start with a README and CI.
Github mirror of MediaWiki extension Newsletter - our actual code is hosted with Gerrit (please see https://www.mediawiki.org/wiki/Developer_access for contributing
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (78).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3README12pt
Add a README.md describing what the project does, how to install it, and how to run it.
- 4Install and run instructions9pt
Add a section showing how to install dependencies.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
20
No README found in the repository.
→ Add a README.md describing what the project does, how to install it, and how to run it.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
Licensed under GPL-2.0.
Engineering
48
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (tests).
PHP linting configured (.eslintrc.json).
Project health
100
Dependency manifest found (composer.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 7Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 7Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files22 root entries
- .phan
- i18n
- includes
- maintenance
- modules
- sql
- testsGood: Test files detected (tests).
- .eslintignore
- .eslintrc.jsonGood: PHP linting configured (.eslintrc.json).
- .gitignoreGood: .gitignore present.
- .gitreview
- .phpcs.xml
- .stylelintrc.json
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- composer.jsonGood: Dependency manifest found (composer.json).
- COPYING
- extension.json
- Gruntfile.js
- Newsletter.alias.php
- Newsletter.namespaces.php
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/wikimedia/mediawiki-extensions-newsletter)