jesseduffield/lazygit
Grade a repo

99

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide.

Top 3% of 5,156 graded repos

simple terminal UI for git commands

Documentation93
Engineering100
Health100
Go82,767MIT9d ago

Outstanding. A score of 98/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

5 to address
  1. 1
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  2. 2
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

  3. 3
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

  4. 4
    Contributing guide5pt

    Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

100

Tests18pt100

Test files detected (pkg/cheatsheet/generate_test.go).

CI/CD14pt100

CI is configured (.github/workflows/check-required-label.yml).

Linting and formatting5pt100

Formatting enforced (.editorconfig).

Reproducibility6pt100

Lockfile present (go.sum). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 120 / 485
    Commits (30d / 90d)
  • 3,047
    Forks
  • 188
    Releaseslatest 8y ago

Community

  • 85% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 82,767
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 2h
    Median PR merge time
  • 1,060
    Open issues
Repository files35 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/check-required-label.yml).
    Good: Dependabot covers 2 ecosystems (gomod, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • cmd
  • demo
  • docs
  • docs-master
  • pkg
    Good: Code of conduct present.
    Good: Test files detected (pkg/cheatsheet/generate_test.go).
  • schema
  • schema-master
  • scripts
  • test
  • vendor
    Good: Security policy present.
  • .editorconfig
    Good: Formatting enforced (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
  • .goreleaser.yml
  • AGENTS.md
  • CLAUDE.md
  • CODE-OF-CONDUCT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • default.nix
  • Dockerfile
  • flake.lock
  • flake.nix
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • justfile
  • LICENSE
    Good: Licensed under MIT.
  • main.go
  • Makefile
  • README.md
    Good: 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.
  • shell.nix
  • VISION.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/jesseduffield/lazygit)](https://www.repo-grade.com/report/jesseduffield/lazygit)

More graded Go repos