0
/ 100
Polished and well engineered. Punching above its star count.
A Python API for working with Neurodata stored in the NWB Format
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 lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
72
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Other.
Engineering
90
Lockfile present (requirements.txt). Installs are reproducible.
CI is configured (.github/workflows/check_sphinx_links.yml).
Test files detected (tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Issue or PR templates present.
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)
- 94Forks
- 48Releaseslatest 7y ago
Community
- -Community health
- -authors own >50% of commits
- 218Watchers
Responsiveness
- 63d 20hMedian issue response
- <1hMedian PR merge time
- 273Open issues
Repository files23 root entries
- .githubGood: Code of conduct present.Good: CI is configured (.github/workflows/check_sphinx_links.yml).Good: Issue or PR templates present.
- docsGood: 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.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.
- scripts
- src
- testsGood: Test files detected (tests).
- .codecov.yml
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .readthedocs.yaml
- CHANGELOG.md
- environment-ros3.yml
- Legal.txt
- license.txtGood: Licensed under Other.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.rstGood: README is present.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.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.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.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-dev.txt
- requirements-doc.txt
- requirements-min.txt
- requirements-opt.txt
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- test.py
- tox.ini
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/neurodatawithoutborders/pynwb)