gitlabhq/gitlab-runner
Grade a repo

84

/ 100

GradeB

Good shape overall. A few tweaks would push it into the top tier.

Top 24% of 5,156 graded repos

Mirror | Please open new issues in our issue tracker on GitLab.com

Documentation74
Engineering86
Health94
Go245MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  2. 2
    Install and run instructions9pt

    Add a section showing how to start or use the project.

  3. 3
    Install and run instructions9pt

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

  4. 4
    Reproducibility6pt

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

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

74

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt67

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under MIT.

Engineering

86

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt85

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

Tests18pt100

Test files detected (cache/adapter_test.go).

CI/CD14pt100

CI is configured (.gitlab-ci.yml).

Linting and formatting5pt100

Formatting enforced (.editorconfig).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 31 / 210
    Commits (30d / 90d)
  • 86
    Forks
  • 0
    Releases

Community

  • 50% - Fair
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 245
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files59 root entries
  • .gitlab
  • .vscode
  • apps
  • cache
    Good: Test files detected (cache/adapter_test.go).
  • certs
  • ci
  • commands
  • common
  • dockerfiles
    Good: Environment pinned via dockerfiles/runner-helper/Dockerfile.
  • docs
  • docs-locale
  • executors
  • functions
  • helpers
  • log
  • magefiles
  • network
  • packaging
  • referees
  • router
  • scripts
  • session
  • shells
  • steps
  • tests
  • .dockerignore
  • .editorconfig
    Good: Formatting enforced (.editorconfig).
  • .env
    Issue: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • .flaky-tests.txt
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .golangci.yml
  • .labkit_logging_todo.yml
  • .markdownlint-cli2.yaml
  • .mockery.yaml
  • .tool-versions
  • .vale.ini
  • AGENTS.md
  • argo_translation.yml
  • CHANGELOG.md
  • config.toml.example
  • 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.
  • Dangerfile
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under MIT.
  • main_test.go
  • main.go
  • Makefile
  • Makefile.build.mk
  • Makefile.runner_helper.mk
  • NOTICE
  • PROCESS.md
  • Procfile
  • PROVENANCE.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • Vagrantfile
  • VERSION
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/gitlabhq/gitlab-runner)](https://www.repo-grade.com/report/gitlabhq/gitlab-runner)

More graded Go repos