Good shape overall. A few tweaks would push it into the top tier.
Rtree: spatial index for Python GIS
Documentation
72
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.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
82
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/test.yml).
Lockfile present (docs/requirements.txt). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
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)
- 129Forks
- 17Releaseslatest 3y ago
Community
- —Community health
- —authors own >50% of commits
- 682Watchers
Responsiveness
- 2hMedian issue response
- 2hMedian PR merge time
- 29Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).Good: Dependabot configured for github-actions.
- benchmarks
- docsGood: Lockfile present (docs/requirements.txt). Installs are reproducible.
- rtree
- scripts
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .readthedocs.yaml
- CHANGES.rst
- CREDITS.txt
- DEPENDENCIES.txt
- environment.ymlGood: Environment pinned via environment.yml.
- FAQ.txt
- LICENSE.txtGood: Licensed under MIT.
- MANIFEST.in
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.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.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.
- setup.py
- tox.ini