onlymate918/rocketmq

0

/ 100

Documentation82
Engineering66
Health68
0Apache-2.01y ago
Grade a repo

Solid engineering. The main gap is visibility.

Apache RocketMQ is a cloud native messaging and streaming platform, making it simple to build event-driven applications.

Documentation

82

README12pt70

README is present.

Contributing guide5pt75

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

66

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

Tests18pt80

Test files detected (acl/src/test).

CI/CD14pt85

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Activity5pt20

No pushes in over a year (−80 pts).

→ A recent commit signals the project is alive and worth contributing to.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (pom.xml).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files38 root entries
  • .github
    Good: CI is configured (.github/workflows/integration-test.yml).
    Good: Issue or PR templates present.
  • acl
    Good: Test files detected (acl/src/test).
  • auth
  • bazel
  • broker
  • client
  • common
  • container
  • controller
  • dev
  • distribution
  • docs
  • example
  • filter
  • namesrv
  • openmessaging
  • proxy
  • remoting
  • srvutil
  • store
  • style
  • test
  • tieredstore
  • tools
  • .asf.yaml
  • .bazelrc
  • .bazelversion
  • .gitignore
    Good: .gitignore present.
  • .licenserc.yaml
  • BUILD.bazel
  • BUILDING
  • 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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    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.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.bazel
  • NOTICE
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
  • WORKSPACE