Getting some notice. Tests and CI would be the fastest wins.
Benchmark results for free-threaded builds of Python
Documentation
88
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.
This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.
README documents how to install the project.
Licensed under BSD-3-Clause.
Engineering
25
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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.
CI is configured (.github/workflows/ci.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Project health
89
Repository has a description.
Dependency manifest found (requirements.txt).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 5Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 29Watchers
Responsiveness
- 5hMedian issue response
- <1hMedian PR merge time
- 2Open issues
Repository files21 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- results
- .gitignoreGood: .gitignore present.
- bench_runner.toml
- benchmarks.manifest
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- configs.json
- configs.svg
- CONTRIBUTING.mdIssue: 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.
- failures.md
- LICENSEGood: Licensed under BSD-3-Clause.
- longitudinal.json
- longitudinal.svg
- loops.json
- memory_configs.json
- memory_configs.svg
- memory_long.json
- memory_long.svg
- README.mdGood: 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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- RESULTS.md