celery/kombu

Messaging library for Python.

View on GitHub ↗Jump to charts ↓Open shareable report →

celery/kombu has 3k+ stars and 1k+ forks on GitHub, is written in Python, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 22nd, 2026
Created on June 23rd, 2010
Open Issues & Pull Requests: 228 (+0)
GitHub issues: Enabled
Number of forks: 1,080
Total Stargazers: 3,149 (+0)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 46.7 hours
Mean response time: 104.9 days
90th percentile: 233.0 days
Tracked items: 175

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 14% of issues opened in the past year have never received a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Component: Redis Broker" is answered fastest, typically in about 35 hours, while "Issue Type: Enhancement" waits about 3 weeks. 79% of issues opened in the past year have been closed, leaving a working backlog. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 68
New in 7 days: 3
Closed in 7 days: 5
Avg open age: 2,279 days
Stale 30+ days: 50
Stale 90+ days: 13

Recent activity

Opened in 7 days: 3
Closed in 7 days: 5
Comments in 7 days: 1
Events in 7 days: 8

Top labels

  • Issue Type: Bug Report (47)
  • Component: Amazon SQS Broker (25)
  • Component: Redis Broker (16)
  • Issue Type: Enhancement (10)
  • Issue Type: Feature Request (10)
  • Component: pyamqp (9)
  • Issue Type: Documentation (9)
  • Component: AMQP Broker (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kombu is a messaging library for Python that abstracts communication with multiple message brokers behind a unified interface.

The library solves the problem of writing broker-agnostic messaging code by providing a consistent API regardless of whether you use RabbitMQ, Redis, Amazon SQS, or other supported transports. Rather than binding your application logic to a specific broker's protocol, Kombu lets you write once and switch brokers by changing configuration. It handles the translation between your code and each broker's native messaging semantics, managing connections, message serialization, and routing patterns.

Kombu is the right choice if you need to decouple your application from a specific message broker or want the flexibility to change brokers without rewriting messaging code. It suits projects that use Celery for distributed task processing, since Celery depends on Kombu for its broker communication. The library is also valuable for any Python application that requires reliable message passing across multiple transport options. If you are building a system where broker independence matters or you anticipate needing to support multiple brokers, Kombu eliminates the need to write adapter code yourself.

The project maintains steady development activity with regular commits addressing bug fixes and feature additions. Pull requests receive timely review and feedback from maintainers. The codebase shows active engagement with issues, including responses to user questions and bug reports. Development follows a structured approach to testing and code quality, with changes evaluated before merging. The project sustains ongoing maintenance rather than operating in a dormant state, indicating continued investment in reliability and compatibility.