96

/ 100

GradeA

A landmark open source project with strong engineering quality.

Top 5% of 5,156 graded repos

Production-Grade Container Scheduling and Management

Go123,299Apache-2.01mo ago

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

Top fixes

Highest-impact changes first, ranked by point weight

9 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
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  3. 3
    Reproducibility6pt

    Remove replace directives before publishing if they point to local paths.

  4. 4
    Contributing guide5pt

    Add setup instructions, code style notes, and how to run tests.

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

90

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

98

Reproducibility6pt85

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

Tests18pt100

Test files detected (LICENSES/vendor/github.com/container-storage-interface/spec).

CI/CD14pt100

CI is configured (vendor/github.com/NYTimes/gziphandler/.travis.yml).

Linting and formatting5pt100

Formatting enforced (vendor/cyphar.com/go-pathrs/.golangci.yml).

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

  • 550 / 1767
    Commits (30d / 90d)
  • 43,355
    Forks
  • 804
    Releaseslatest 11y ago

Community

  • 100% - Good
    Community health
  • 18 bus factor
    authors own >50% of commits
  • 123,299
    Watchers

Responsiveness

  • 2d 11h
    Median issue response
  • <1h
    Median PR merge time
  • 2,756
    Open issues
Repository files36 root entries
  • .github
    Good: Issue or PR templates present.
    Good: Security policy present.
  • api
  • build
    Good: Environment pinned via build/pause/Dockerfile.
  • CHANGELOG
  • cluster
  • cmd
  • docs
  • hack
  • LICENSES
    Good: Test files detected (LICENSES/vendor/github.com/container-storage-interface/spec).
  • logo
  • pkg
  • plugin
  • staging
  • test
  • third_party
  • vendor
    Good: Code of conduct present.
    Good: CI is configured (vendor/github.com/NYTimes/gziphandler/.travis.yml).
    Good: Formatting enforced (vendor/cyphar.com/go-pathrs/.golangci.yml).
  • .generated_files
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .go-version
  • .import-restrictions
  • AGENTS.md
  • CHANGELOG.md
  • code-of-conduct.md
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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).
    Issue: 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • go.work
  • go.work.sum
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • OWNERS
  • OWNERS_ALIASES
  • 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.
  • SECURITY_CONTACTS
  • SUPPORT.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/kubernetes/kubernetes)](https://www.repo-grade.com/report/kubernetes/kubernetes)

More graded Go repos