0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Easy, safe evaluation of arbitrary Python code
Top 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
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
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
86
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
68
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.
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
CI is configured (.github/workflows/build.yaml).
Test files detected (tests).
Linter or formatter configured (.flake8).
Project health
100
Dependency manifest found (pyproject.toml).
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)
- 49Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 280Watchers
Responsiveness
- 12hMedian issue response
- 4d 11hMedian PR merge time
- 11Open issues
Repository files20 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/build.yaml).Good: Dependabot covers 2 ecosystems (docker, github-actions). Dependencies stay current.Good: Security policy present.
- config
- requirements
- scripts
- snekbox
- testsGood: Test files detected (tests).
- .dockerignore
- .flake8Good: Linter or formatter configured (.flake8).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- deployment.yaml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- Dockerfile.pydis
- LICENSEGood: Licensed under MIT.
- LICENSE-THIRD-PARTY
- Makefile
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/python-discord/snekbox)