cloudfoundry/diego-release
Grade a repo

84

/ 100

GradeC

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

Top 35% of 5,156 graded repos

BOSH Release for Diego

Documentation69
Engineering78
Health94
Go206Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

69

README12pt35

README is present.

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/tests-workflow.yml).

Tests18pt80

Test files detected (jobs/auctioneer/spec).

Reproducibility6pt80

Lockfile present (Gemfile.lock). Installs are reproducible.

Linting and formatting5pt100

Ruby linting configured (src/code.cloudfoundry.org/vendor/code.cloudfoundry.org/go-diodes/.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (Gemfile).

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

  • 48 / 116
    Commits (30d / 90d)
  • 221
    Forks
  • 284
    Releaseslatest 10y ago

Community

  • 75% - Good
    Community health
  • 8 bus factor
    authors own >50% of commits
  • 206
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1d 7h
    Median PR merge time
  • 14
    Open issues
Repository files18 root entries
  • .final_builds
    Good: Licensed under Apache-2.0.
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: CI is configured (.github/workflows/tests-workflow.yml).
    Good: Issue or PR templates present.
  • config
  • docs
  • jobs
    Good: Test files detected (jobs/auctioneer/spec).
  • packages
  • releases
  • scripts
  • spec
  • src
    Good: Code of conduct present.
    Good: Ruby linting configured (src/code.cloudfoundry.org/vendor/code.cloudfoundry.org/go-diodes/.golangci.yml).
    Good: Environment pinned via src/code.cloudfoundry.org/vendor/code.cloudfoundry.org/routing-api/docker-compose.yml.
    Good: Security policy present.
    Issue: Build artifacts or local files may be committed (src/code.cloudfoundry.org/vizzini/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • CODEOWNERS
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE
  • NOTICE
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
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/cloudfoundry/diego-release)](https://www.repo-grade.com/report/cloudfoundry/diego-release)

More graded Go repos