91
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Open-source framework for the research and development of foundation models.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a section showing how to start or use the project.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Dependency manifest6pt
Add a [project.urls] table (Homepage, Repository) so PyPI links back to your project.
- 4Dependency manifest6pt
Add `authors = [...]` under [project] so the package has clear ownership.
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
77
README documents how to install the project.
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under Apache-2.0.
Engineering
100
Test files detected (experiments/datakit/store/ops/smoke_test.py).
CI is configured (.github/workflows/ducky-unit.yaml).
Linter or formatter configured (infra/status-page/eslint.config.js).
Lockfile present (uv.lock). Installs are reproducible.
Issue or PR templates present.
Project health
89
.gitignore present.
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 281 / 1132Commits (30d / 90d)
- 135Forks
- 15Releaseslatest 2mo ago
Community
- 75% - GoodCommunity health
- 5 bus factorauthors own >50% of commits
- 1,155Watchers
Responsiveness
- 735d 5hMedian issue response
- 23hMedian PR merge time
- 512Open issues
Repository files30 root entries
- .agents
- .claude
- .githubGood: CI is configured (.github/workflows/ducky-unit.yaml).Good: Dependabot covers 2 ecosystems (uv, npm). Dependencies stay current.Good: Issue or PR templates present.
- config
- docker
- docs
- etc
- experimentsGood: Test files detected (experiments/datakit/store/ops/smoke_test.py).
- infraGood: Linter or formatter configured (infra/status-page/eslint.config.js).Good: Environment pinned via infra/probes/deploy/Dockerfile.
- libIssue: Build artifacts or local files may be committed (lib/levanter/.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
- scripts
- tests
- .dockerignore
- .gitignoreGood: .gitignore present.
- .pyrefly-baseline.json
- .python-version
- .readthedocs.yaml
- AGENTS.md
- AUTHORS.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- mkdocs.yml
- pr_reviews.db
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- TESTING.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/marin-community/marin)