cloudfoundry/diego-release

0

/ 100

Documentation69
Engineering90
Health94
Go206Apache-2.01d ago
Grade a repo

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

BOSH Release for Diego

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

90

Tests18pt80

Test files detected (jobs/auctioneer/spec).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (src/code.cloudfoundry.org/vendor/code.cloudfoundry.org/garden/.drone.yml).

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

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

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 206
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1d 7h
    Median PR merge time
  • 15
    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: 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: CI is configured (src/code.cloudfoundry.org/vendor/code.cloudfoundry.org/garden/.drone.yml).
    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.