Legit

A lightweight, self-hosted web frontend for Git repositories, written in Go, that lets you browse and clone repositories over HTTP/HTTPS with customizable…

  • Development
  • Media Applications
  • Other
  • Productivity
  • Tools & Utilities
A lightweight, self-hosted web frontend for Git repositories, written in Go, that lets you browse and clone repositories over HTTP/HTTPS with customizable templates and stylesheets.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

21/100 Low

Maintained
9last commit 644 days ago
Popular
53470 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
No data
Security check
54 serious findings, 5 minor, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 21 days ago

GitHub stars
470
Open issues
13
Last commit
2025-02-15
Latest release
v0.2.4
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (icyphox/legit)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

Where does legit expect Git repositories to be located?

Set repo.scanPath to the directory containing your Git repositories. It does not traverse subdirectories yet, so repositories should live directly under that path.

Can clients clone non-bare repositories over HTTP or HTTPS?

Cloning over HTTP or HTTPS only works with bare repositories. Non-bare repositories can still be viewed in the web interface, but they are not usable for HTTP cloning.

How do you point legit to a config file outside the current directory?

By default it looks for config.yaml in the current directory. Pass the --config flag to point it to another configuration file.

How can specific repositories be hidden or skipped?

Use repo.ignore to skip repositories relative to scanPath. Use repo.unlisted to hide repositories relative to scanPath.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads