92/ 100 · A
A top-tier open source project. Docs, tests, and CI are all in excellent shape.
The lean application framework for Python. Build sophisticated user interfaces with a simple Python API. Run your apps in the terminal and a web browser.
Python36,268 starsMITupdated 21d ago
DocumentationREADME, setup, examples, license
EngineeringTests, CI, linting, lockfiles
Project healthDescription, activity, stars, deps
What to fix first
The highest-impact improvements for this repo.
- 1CI/CDEngineeringInfo
Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.
- 2CI/CDEngineeringInfo
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CDEngineeringInfo
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
Detailed breakdown
Documentation
96- README100
- README is present.
- README is well structured with multiple sections.
- README includes screenshots or visuals. Great for first impressions.
- README has code examples.
- README links to a live demo or deployed app.
- README includes status badges.
- Install and run instructions90
- README documents how to install the project.
- README documents how to run the project.
- If your project uses environment variables, add a .env.example listing them (+10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
- License100
- Licensed under MIT.
- Contributing guide95
- Contributing guide is detailed and thorough.
- Contributing guide includes setup/install instructions.
- Contributing guide describes code style expectations.
- Contributing guide explains how to run tests.
- Contributing guide lacks a PR workflow section (−8 pts).Explain how to fork, branch, and open a pull request so contributors know what to expect.
- Contributing guide includes code examples.
- Code of conduct present.
Engineering
87- Tests100
- Test files detected (docs/examples/guide/testing/test_rgb.py).
- Pytest is fully configured in pyproject.toml with testpaths and test files detected.
- CI/CD85
Not applicable?
- CI is configured (.github/workflows/pythonpackage.yml).
- CI workflow runs tests.
- CI runs on pull requests, not just on pushes to main.
- CI does not appear to run a linter (−15 pts).Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.
- Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- CI tests across multiple environments or versions.
- Linting and formatting60
- pyproject.toml configures a Python formatter or linter (ruff/black).
- No [tool.mypy] in pyproject.toml (−20 pts vs having both ruff and mypy).Install mypy and add a [tool.mypy] section to pyproject.toml for type checking.
- Reproducibility70
- Lockfile present (poetry.lock). Installs are reproducible.
- No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- Issue and PR templates90
- Issue or PR templates present.
- Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
Project health
100- Dependency manifest100
- Dependency manifest found (pyproject.toml).
- pyproject.toml has a [project] table with package metadata.
- pyproject.toml includes a description.
- pyproject.toml specifies requires-python, preventing installs on incompatible versions.
- pyproject.toml has a [build-system] table. The package can be built and published.
- Repository metadata100
- Repository has a description.
- Primary language detected: Python.
- pyproject.toml [project] metadata is complete (description, authors, urls).
- Activity100
- Actively maintained (pushed within the last month).
- 36,268 stars.
- Housekeeping100
- .gitignore present.
Repository files32 root entries
- .faq
- .githubGood: CI is configured (.github/workflows/pythonpackage.yml).Good: Issue or PR templates present.
- docsGood: Test files detected (docs/examples/guide/testing/test_rgb.py).
- examples
- imgs
- notes
- questions
- reference
- src
- tests
- tools
- .coveragerc
- .deepsource.toml
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- AI_POLICY.md
- CHANGELOG.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Info: 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.Good: Contributing guide includes code examples.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.md
- docs.md
- faq.yml
- LICENSEGood: Licensed under MIT.
- Makefile
- mkdocs-common.yml
- mkdocs-nav.yml
- mkdocs-offline.yml
- mkdocs-online.yml
- mypy.ini
- poetry.lockGood: Lockfile present (poetry.lock). Installs are reproducible.
- 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.
- uv.lock