cloudfoundry/java-buildpack
Grade a repo

0

/ 100

GradeB

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

Top 28% of 5,156 graded repos

Cloud Foundry buildpack for running Java applications

Documentation85
Engineering74
Health100
Go453Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    CI/CD14pt

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

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

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

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

85

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

74

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.

CI/CD14pt57

CI is configured (.github/workflows/test-pull-request.yml).

Reproducibility6pt85

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

Tests18pt100

Test files detected (src/integration/dist_zip_test.go).

Linting and formatting5pt100

Formatting enforced (vendor/github.com/Masterminds/semver/v3/.golangci.yml).

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)
  • 2,548
    Forks
  • 138
    Releaseslatest 11y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 453
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 5
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/test-pull-request.yml).
  • bin
  • ci
    Good: Environment pinned via ci/Dockerfile.
  • docs
    Good: Security policy present.
  • scripts
  • src
    Good: Test files detected (src/integration/dist_zip_test.go).
  • vendor
    Good: Code of conduct present.
    Good: Formatting enforced (vendor/github.com/Masterminds/semver/v3/.golangci.yml).
  • .envrc
  • .gitignore
    Good: .gitignore present.
  • adoption-migration-details.md
  • ARCHITECTURE.md
  • config.json
  • 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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    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.
  • java-buildpack.iml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • manifest.yml
  • 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.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    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.
  • RUBY_VS_GO_BUILDPACK_COMPARISON.md
  • 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/cloudfoundry/java-buildpack)](https://www.repo-grade.com/report/cloudfoundry/java-buildpack)

More graded Go repos