0

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Top 10% of 5,156 graded repos

Apache Celeborn is an elastic and high-performance service for shuffle and spilled data.

Java1,053Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

7 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
    Install and run instructions9pt

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

  3. 3
    Reproducibility6pt

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

  4. 4
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

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

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

90

Tests18pt80

Test files detected (charts/celeborn/tests).

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/check_stale_prs.yml).

Linting and formatting5pt100

Java/Kotlin linting configured (web/.eslintrc.cjs).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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)
  • 447
    Forks
  • 23
    Releaseslatest 2y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,053
    Watchers

Responsiveness

  • 21h
    Median issue response
  • 12h
    Median PR merge time
  • 25
    Open issues
Repository files50 root entries
  • .github
    Good: Licensed under Apache-2.0.
    Good: CI is configured (.github/workflows/check_stale_prs.yml).
    Good: Issue or PR templates present.
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/icon.png) (−40 pts).Fix: Remove them and add to .gitignore.
  • .mvn
  • assets
  • bin
  • build
  • charts
    Good: Test files detected (charts/celeborn/tests).
  • cli
  • client
  • client-flink
  • client-mr
  • client-spark
  • client-tez
  • common
  • conf
  • cpp
  • dev
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • docs
    Good: Security policy present.
  • licenses-binary
  • lifecycle-manager
  • master
  • multipart-uploader
  • openapi
  • project
  • rust
  • sbin
  • service
  • spi
  • tests
  • toolkit
  • web
    Good: Java/Kotlin linting configured (web/.eslintrc.cjs).
  • worker
  • .asf.yaml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .rat-excludes
  • .scalafmt.conf
  • codecov.yml
  • 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.
    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.
    Good: Contributing guide includes code examples.
  • LICENSE
  • LICENSE-binary
  • Makefile
  • mkdocs.yml
  • NOTICE
  • NOTICE-binary
  • 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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • version.sbt
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/apache/celeborn)](https://www.repo-grade.com/report/apache/celeborn)

More graded Java repos