Repo brief: apache/pulsar

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T10:25:28.305Z · commit 67205b946b76

Verdict

Healthy — Strong maintenance signals

• Last commit today
• 20 active contributors
• Apache-2.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Apache Pulsar is a distributed pub-sub messaging system designed for horizontally scalable, low-latency message delivery across millions of independent topics. It combines durable storage (via BookKeeper), flexible topic/queue semantics, multi-tenant architecture with authentication/authorization, and strong ordering guarantees—solving the problem of building scalable, reliable message brokers for both streaming and queuing use cases. Monorepo with clear layering: bin/ contains CLI entry points (pulsar, pulsar-admin, pulsar-client, pulsar-perf, pulsar-shell), build-logic/conventions/ houses Gradle plugins and shared build configuration (shading, code quality, NAR packaging), and…

Start here

Open these first:

• build.gradle.kts — Root Gradle build configuration defining the multi-module project structure, dependencies, and build lifecycle for the…
• ARCHITECTURE.md — Comprehensive architectural overview documenting the design, components, and relationships within the Pulsar distributed…
• conf/broker.conf — Core broker configuration template defining all runtime parameters for Pulsar message brokers in production deployments.
• bin/pulsar — Primary CLI entry point for starting and managing Pulsar broker instances and cluster operations.
• CONTRIBUTING.md — Developer contribution guidelines documenting code style, testing requirements, and submission process for this Apache…

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone and prepare the workspace:

git clone https://github.com/apache/pulsar.git
cd pulsar

Verify Gradle wrapper and build prerequisites: the repository uses Gradle (evidenced by build-logic/settings.gradle.kts) and appears to require Java. Consult the root build.gradle.kts (not shown in file list) and CONT…

Daily commands:

Exact invocation depends on recognizing the build system from root manifests (not fully shown). Standard Gradle workflow: ./gradlew build for compilation, ./gradlew test for unit tests. CLI binaries (pulsar, pulsar-…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 56% of recent commits
• Multi-language protobuf regeneration is error-prone: update_python_protobuf_stubs.sh must be run when .proto files change, with a Docker variant available if the local protoc version diverges. Shading is mandatory…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.