project-zot/zot

0

/ 100

Documentation62
Engineering100
Health100
Go2,394Apache-2.0today
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

zot - A scale-out production-ready vendor-neutral OCI-native container image/artifact registry (purely based on OCI Distribution Specification)

Documentation

62

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt78

README is present.

Contributing guide5pt89

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

100

Tests18pt100

Test files detected (cmd/zb/main_test.go).

CI/CD14pt100

CI is configured (.github/workflows/build.yaml).

Linting and formatting5pt100

Formatting enforced (.golangci.yaml).

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

  • —
    Commits (30d / 90d)
  • 231
    Forks
  • 118
    Releaseslatest 6y ago

Community

  • 100% - Good
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 2,394
    Watchers

Responsiveness

  • 16d 20h
    Median issue response
  • 1h
    Median PR merge time
  • 75
    Open issues
Repository files32 root entries
  • .github
    Good: Licensed under Apache-2.0.
    Good: CI is configured (.github/workflows/build.yaml).
    Good: Dependabot covers 2 ecosystems (gomod, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .zap
  • build
    Good: Environment pinned via build/Dockerfile.
  • cmd
    Good: Test files detected (cmd/zb/main_test.go).
  • demos
  • docs
  • errors
  • examples
  • pkg
  • scripts
  • swagger
  • test
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .golangci.yaml
    Good: Formatting enforced (.golangci.yaml).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • CODEOWNERS
  • COMPARISON.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
  • MAINTAINERS.md
  • Makefile
  • NOTICE
  • README_fuzz.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • README.md
  • SECURITY.md
    Good: Security policy present.
  • THIRD-PARTY-LICENSES.md
  • tools.go
  • zot.go