94
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
An implementation of chunked, compressed, N-dimensional arrays for Python.
Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Contributing guide5pt
Describe your linting/formatting rules and how to run them.
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
96
README documents how to install the project.
Contributing guide is detailed and thorough.
README is present.
Licensed under MIT.
Engineering
96
CI is configured (.github/workflows/check_changelogs.yml).
Test files detected (packages/zarr-metadata/tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Lockfile present (uv.lock). Installs are reproducible.
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
- 30 / 109Commits (30d / 90d)
- 423Forks
- 105Releaseslatest 9y ago
Community
- 87% - GoodCommunity health
- 4 bus factorauthors own >50% of commits
- 2,008Watchers
Responsiveness
- 2d 20hMedian issue response
- 20hMedian PR merge time
- 513Open issues
Repository files26 root entries
- .githubGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.Good: CI is configured (.github/workflows/check_changelogs.yml).Good: Dependabot covers 3 ecosystems (github-actions, uv, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- bench
- changes
- ci
- design
- docs
- examples
- packagesGood: Test files detected (packages/zarr-metadata/tests).
- src
- tests
- .git_archival.txt
- .git-blame-ignore-revs
- .gitattributes
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .python-versionGood: Environment pinned via .python-version.
- .pyup.yml
- .readthedocs.yaml
- codecov.yml
- FUNDING.yml
- LICENSE.txtGood: Licensed under MIT.
- mkdocs.yml
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- TEAM.md
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/zarr-developers/zarr-python)