exercism/python

0

/ 100

Documentation75
Engineering92
Health100
Python2,428MIT1d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Exercism exercises in Python.

Documentation

75

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

README12pt78

README is present.

Contributing guide5pt93

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

92

Tests18pt80

Test files detected (bin/test_exercises.py).

Reproducibility6pt92

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

CI/CD14pt100

CI is configured (.github/workflows/ci-workflow.yml).

Linting and formatting5pt100

Linter or formatter configured (.flake8).

Issue and PR templates6pt100

Issue or PR templates present.

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)
  • 1,498
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,428
    Watchers

Responsiveness

  • 7h
    Median issue response
  • <1h
    Median PR merge time
  • 28
    Open issues
Repository files21 root entries
  • .appends
  • .github
    Good: CI is configured (.github/workflows/ci-workflow.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • bin
    Good: Test files detected (bin/test_exercises.py).
  • concepts
  • config
  • docs
  • exercises
  • reference
  • .flake8
    Good: Linter or formatter configured (.flake8).
  • .gitignore
    Good: .gitignore present.
  • .style.yapf
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • config.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • LICENSE
    Good: Licensed under MIT.
  • pylintrc
  • pytest.ini
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## 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.
  • requirements-generator.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).