93
/ 100
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
Pretrain, finetune ANY AI model of ANY size on 1 or 10,000+ GPUs with zero code changes.
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.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
94
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
94
CI is configured (.github/workflows/ci-check-md-links.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Issue or PR templates present.
Project health
88
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
- 7 / 58Commits (30d / 90d)
- 3,754Forks
- 174Releaseslatest 6y ago
Community
- 87% - GoodCommunity health
- 4 bus factorauthors own >50% of commits
- 31,218Watchers
Responsiveness
- 4hMedian issue response
- <1hMedian PR merge time
- 1,035Open issues
Repository files23 root entries
- .actions
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/ci-check-md-links.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .lightning
- docs
- examples
- requirements
- src
- testsGood: Test files detected (tests).
- _notebooks
- .codecov.yml
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .gitmodules
- .pre-commit-config.yaml
- .readthedocs.yml
- CITATION.cff
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- 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.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.
- SECURITY.mdGood: Security policy present.
- setup.py
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/lightning-ai/pytorch-lightning)