mxsm/rocketmq-rustNew scan
99/ 100 · A

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

🚀Apache RocketMQ build in Rust🦀. Faster, safer, and with lower memory usage. ⭐ Star to support our work❤️!

Rust1,495 starsApache-2.0updated today

Outstanding work. A score of 99/100 puts this repo in a very small tier of truly well-engineered open source projects.

DocumentationREADME, setup, examples, license
96
EngineeringTests, CI, linting, lockfiles
100
Project healthDescription, activity, stars, deps
100

What to fix first

The highest-impact improvements for this repo.

  1. 1
    Install and run instructions
    DocumentationIssue

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

  2. 2
    Issue and PR templates
    EngineeringInfo

    A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

  3. 3
    Contributing guide
    DocumentationIssue

    Add setup instructions, code style notes, and how to run tests.

Detailed breakdown

Documentation

96
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • No .env.example found (−10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under Apache-2.0.
  • Contributing guide91
    • Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Add setup instructions, code style notes, and how to run tests.
    • Contributing guide includes setup/install instructions.
    • Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them.
    • Contributing guide explains how to run tests.
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Code of conduct present.

Engineering

100
  • Tests100
    • Test files detected (rocketmq-auth/tests).
    • Rust workspace with test files detected. Run with `cargo test --workspace`.
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/dashboard-tauri-ci.yml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • CI runs type checking (tsc, mypy, cargo check, etc.).
    • CI reports or uploads test coverage.
    • CI tests across multiple environments or versions.
    • CI includes a build step.
  • Linting and formatting100
    • Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
  • Reproducibility100
    • Lockfile present (Cargo.lock). Installs are reproducible.
    • Environment pinned via docker/Dockerfile.
    • Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

Project health

100
  • Dependency manifest100
    • Dependency manifest found (Cargo.toml).
    • Cargo.toml is a workspace manifest for a multi-crate Rust project.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 1,495 stars.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 244
    Forks
  • 9
    Releaseslatest 8d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,495
    Watchers

Responsiveness

  • 328d 21h
    Median issue response
  • <1h
    Median PR merge time
  • 33
    Open issues
Repository files44 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/dashboard-tauri-ci.yml).
    Good: Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • distribution
  • docker
    Good: Environment pinned via docker/Dockerfile.
  • resources
  • rocketmq
  • rocketmq-auth
    Good: Test files detected (rocketmq-auth/tests).
  • rocketmq-broker
  • rocketmq-client
  • rocketmq-common
  • rocketmq-controller
  • rocketmq-dashboard
  • rocketmq-doc
  • rocketmq-error
  • rocketmq-example
  • rocketmq-filter
  • rocketmq-macros
  • rocketmq-namesrv
  • rocketmq-observability
  • rocketmq-proxy
  • rocketmq-remoting
  • rocketmq-runtime
  • rocketmq-store
  • rocketmq-tieredstore
  • rocketmq-tools
  • rocketmq-website
  • scripts
  • .clippy.toml
  • .coderabbit.yaml
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
  • LICENSE-APACHE
  • NOTICE
  • README-zh_cn.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.
  • README.md
  • rust-toolchain.toml
  • rustfmt.toml
    Good: Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).