81/ 100 · B
Popular and well-maintained. A little polish away from elite status.
Typer, build great CLIs. Easy to code. Based on Python type hints.
Python19,562 starsMITupdated 5d 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/CDEngineeringWarning
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CDEngineeringInfo
Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.
- 3CI/CDEngineeringInfo
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
Detailed breakdown
Documentation
86- README80
- README is present.
- README is well structured with multiple sections.
- No screenshots or images in the README (−20 pts).Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 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 guide74
- Contributing guide is detailed and thorough.
- Contributing guide includes setup/install instructions.
- Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
- Contributing guide lacks a testing section (−8 pts).Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
- 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.
- Optional: add a Code of Conduct (+5 pts).A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.
Engineering
74- Tests95
- Test files detected (docs_src/testing/app01_py310/test_main.py).
- Pytest referenced in pyproject.toml and test files present.
- Coverage reporting is configured in pyproject.toml.
- CI/CD57
Not applicable?
- CI is configured (.github/workflows/build-docs.yml).
- The CI workflow does not appear to run any tests (−28 pts).Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 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.
- CI reports or uploads test coverage.
- CI caches dependencies for faster runs.
- CI tests across multiple environments or versions.
- Linting and formatting100
- pyproject.toml configures both a formatter/linter (ruff/black) and type checking (mypy).
- Reproducibility100
- Lockfile present (uv.lock). Installs are reproducible.
- Environment pinned via scripts/docker/Dockerfile.
- Dependabot covers 3 ecosystems (github-actions, uv, pre-commit). Dependencies stay current.
- Issue and PR templates0
- No issue or PR templates found (−90 pts).Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.
Project health
94- 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).
- 19,562 stars.
- Housekeeping60
- .gitignore present.
- Build artifacts or local files may be committed (.env) (−40 pts).Remove them and add to .gitignore.
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/build-docs.yml).Good: Dependabot covers 3 ecosystems (github-actions, uv, pre-commit). Dependencies stay current.
- docsGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Info: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).Info: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).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.
- docs_srcGood: Test files detected (docs_src/testing/app01_py310/test_main.py).
- scriptsGood: Environment pinned via scripts/docker/Dockerfile.
- tests
- typer
- .envWarning: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- .python-version
- CITATION.cff
- LICENSEGood: Licensed under MIT.
- mkdocs.env.yml
- mkdocs.yml
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Warning: 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.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.lockGood: Lockfile present (uv.lock). Installs are reproducible.