eclipse-jkube/jkube
Grade a repo

78

/ 100

GradeC

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

Top 35% of 5,156 graded repos

Build and Deploy java applications on Kubernetes

Documentation90
Engineering62
Health100
Java849EPL-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

    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

90

Contributing guide5pt55

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 EPL-2.0.

Engineering

62

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

Reproducibility6pt30

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/build-macos.yml).

Tests18pt80

Test files detected (gradle-plugin/it/src/it/configmap/src/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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

  • 19 / 23
    Commits (30d / 90d)
  • 550
    Forks
  • 39
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 13d 22h
    Median issue response
  • 16h
    Median PR merge time
  • 158
    Open issues
Repository files34 root entries
  • .claude
  • .github
    Good: Licensed under EPL-2.0.
    Good: CI is configured (.github/workflows/build-macos.yml).
    Good: Dependabot covers 2 ecosystems (maven, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .jenkins
  • .mvn
  • gradle-plugin
    Good: Test files detected (gradle-plugin/it/src/it/configmap/src/test).
    Good: Environment pinned via gradle-plugin/it/src/it/dockerfile-simple-generator-precedence-kubernetes/Dockerfile.
  • ide-config
  • jkube-kit
  • kubernetes-maven-plugin
  • media
  • openshift-maven-plugin
  • quickstarts
  • scripts
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitpod.yml
  • ADOPTERS.md
  • AGENTS.md
  • BUILDING.md
  • CHANGELOG.md
  • CLAUDE.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).
    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.
  • devfile.yaml
  • header.txt
  • Jenkinsfile
  • jitpack.yml
  • LICENSE
  • MIGRATION-GUIDE.md
  • mvnw
  • mvnw.cmd
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
  • REBRANDING.md
  • SECURITY.md
    Good: Security policy present.
  • USING-SNAPSHOT-ARTIFACTS.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/eclipse-jkube/jkube)](https://www.repo-grade.com/report/eclipse-jkube/jkube)

More graded Java repos