IBM/sarama

Sarama is a Go library for Apache Kafka.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 31 minutes ago
Added to GitGenius on March 8th, 2026
Created on July 5th, 2013
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 1,864
Total Stargazers: 12,515 (+0)
Total Subscribers: 608 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.9 days
Mean response time: 262.8 days
90th percentile: 1164.0 days
Tracked items: 167

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 6% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 608 days
Stale 30+ days: 8
Stale 90+ days: 2

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • stale (106)
  • needs-investigation (45)
  • stale/exempt (30)
  • bug (10)
  • Feature request (3)
  • enhancement (3)
  • question (3)
  • v2 (3)

Most active issues this week

Detailed Description

Sarama is a Go client library for Apache Kafka.

Sarama solves the problem of integrating Kafka messaging into Go applications by providing a native client implementation. The library handles both producer and consumer operations, allowing applications to send messages to and read messages from Kafka clusters. It abstracts away the complexity of the Kafka protocol, exposing a Go-idiomatic API for common messaging patterns.

Developers should choose Sarama if they are building Go services that need to interact with Kafka. The library suits projects ranging from simple message producers and consumers to more complex streaming applications. Sarama includes testing utilities through its mocks subpackage, command-line tools for diagnostics and instrumentation, and comprehensive examples demonstrating various use cases. The project maintains compatibility with the two latest stable releases of Kafka and Go, with a two-month grace period for older versions, though earlier Kafka releases are likely to remain functional.

The project typically responds to issues and pull requests within one to two weeks. Work in the issue tracker centers on bug fixes, enhancements, and management of stale items, indicating a focus on stability and incremental improvement rather than rapid feature expansion.