Apache Kafka® compatible broker with S3, PostgreSQL, SQLite, Apache Iceberg and Delta Lake
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 13%
Response Time: 3h
First Timer Success: -
nisshi-io/nisshi has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nisshi-io/nisshi respond to incoming external pull requests in approximately 3.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 57.0 places nisshi-io/nisshi in the A tier.
The external contributor pull request merge rate for nisshi-io/nisshi is 13.3%, based on public PR activity from non-core contributors.
nisshi-io/nisshi currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in nisshi-io/nisshi. Reviews community pull requests with focus on project quality.
Discussions in nisshi-io/nisshi focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/nisshi-io/nisshi?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (9% approval). Large PRs (>500 lines) take ~88 hours (15% approval). Keep your diff compact for rapid review.
Does it make sense to apply the cleanup.policy to dynostore (S3, memory/etc) based storage engines? Yes, it makes sense to apply cleanup.policy (delete/compact) to dynostore-based backends like S3. Tansu aims to be a drop in replacement for Apache Kafka. In Kafka, cleanup.policy is a core topic configuration that works regardless of the underlying storage (log segments on disk). Users expect the same behavior when they set cleanup.policy=delete or compact (or both) on a topic; especially for S3-backed setups, which are often used for cost-effective, long-term or high-volume storage. One additional suggestion I want to add is in the docs to make this clear explicitly; during the time it is being built. It took me a issue search to figure this out; that the above support is not fully ready. Without this; I see that people using the S3 engine (or S3 compatible ones) will configure topics with retention and compaction policies; expecting it to work. Without enforcement, data will just keep
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to nisshi-io/nisshi, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of nisshi-io/nisshi acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 13.3% were successfully merged into the primary branch.
nisshi-io/nisshi has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 57.0 places nisshi-io/nisshi in the Welcoming tier.
The external pull request merge rate is 13.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nisshi-io/nisshi currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for nisshi-io/nisshi are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.