77
/ 100
Solid foundation. Invest in docs and CI to grow from here.
Curated list of open Call-for-Papers in SE/PL scientific conferences: we keep an eye on all of them!
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 3README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
58
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
80
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 (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/check-links.yml).
Test files detected (test_compile.py).
Linter or formatter configured (ruff.toml).
Project health
100
Dependency manifest found (requirements.txt).
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
- 42% - WeakCommunity health
- -authors own >50% of commits
- 18Watchers
Responsiveness
- <1hMedian issue response
- 3hMedian PR merge time
- 10Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/check-links.yml).
- fixtures
- LICENSES
- .gitignoreGood: .gitignore present.
- .markdownlint-cli2.jsonc
- .rultor.yml
- .yamllint.yml
- cfp.yml
- compile.py
- LICENSE.txtGood: Licensed under MIT.
- README.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- renovate.json
- requirements.in
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- REUSE.toml
- ruff.tomlGood: Linter or formatter configured (ruff.toml).
- setup.cfg
- test_compile.pyGood: Test files detected (test_compile.py).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/yegor256/awesome-cfp)