mychewcents/ctfd
Grade a repo

0

/ 100

GradeB

Polished work that hasn't found its audience yet.

Top 16% of 5,156 graded repos

CTFs as you need them

Documentation91
Engineering90
Health75
Python1Apache-2.05y ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  4. 4
    Reproducibility6pt

    Use a multi-stage Dockerfile.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

91

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

90

Tests18pt80

Test files detected (tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/lint.yml).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

75

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files39 root entries
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Issue or PR templates present.
  • conf
  • CS2107
  • CTFd
  • migrations
  • scripts
  • tests
    Good: Test files detected (tests).
  • .codecov.yml
  • .dockerignore
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .flaskenv
  • .gitignore
    Good: .gitignore present.
  • .isort.cfg
  • .prettierignore
  • CHANGELOG.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • ctfd.service
  • development.txt
  • docker-compose.yml
  • docker-entrypoint.sh
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • export.py
  • import.py
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • manage.py
  • package.json
    Good: Dependency manifest found (package.json).
  • ping.py
  • populate.py
  • prepare.sh
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements.in
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • serve.py
  • setup.cfg
  • Vagrantfile
  • webpack.config.js
  • wsgi.py
  • yarn.lock
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/mychewcents/ctfd)](https://www.repo-grade.com/report/mychewcents/ctfd)

More graded Python repos