yegor256/awesome-cfp

0

/ 100

Documentation58
Engineering80
Health100
Python18MIT1d ago
Grade a repo

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!

Documentation

58

Contributing guide5pt0

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.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt70

README is present.

License6pt100

Licensed under MIT.

Engineering

80

Issue and PR templates6pt0

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.

Reproducibility6pt70

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/check-links.yml).

Tests18pt100

Test files detected (test_compile.py).

Linting and formatting5pt100

Linter or formatter configured (ruff.toml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 7
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 18
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 3h
    Median PR merge time
  • 10
    Open issues
Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/check-links.yml).
  • fixtures
  • LICENSES
  • .gitignore
    Good: .gitignore present.
  • .markdownlint-cli2.jsonc
  • .rultor.yml
  • .yamllint.yml
  • cfp.yml
  • compile.py
  • LICENSE.txt
    Good: Licensed under MIT.
  • README.md
    Good: 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.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • REUSE.toml
  • ruff.toml
    Good: Linter or formatter configured (ruff.toml).
  • setup.cfg
  • test_compile.py
    Good: Test files detected (test_compile.py).