kenn-io/kata - Open Source PR Review Scorecard

Local-first issue tracking for AI-assisted software work, with an agent-friendly CLI and human-facing TUI

C-Rank Grade: A (Welcoming) - 64/100

External PR Merge Rate: 93%

Response Time: 7d

First Timer Success: 73%

Frequently Asked Questions

Is kenn-io/kata welcoming to first-time open-source contributors?

kenn-io/kata has a recorded first-timer success rate of 72.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in kenn-io/kata respond to incoming external pull requests in approximately 168.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 64.4 C-Rank™ score (A Tier) represent?

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 64.4 places kenn-io/kata in the A tier.

What is the external contributor pull request merge rate for kenn-io/kata?

The external contributor pull request merge rate for kenn-io/kata is 93.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in kenn-io/kata?

kenn-io/kata does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

kenn-io
kenn-io/kataAWelcoming395
GitHub
Back to Explorer
kenn-io

kenn-io/kata

395
AWelcoming(64/100)Go

Local-first issue tracking for AI-assisted software work, with an agent-friendly CLI and human-facing TUI

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
6.8/10
Patience Score
7.4/10
Nitpick Rate
40%

Rigorous architecture standards (61% critical review signals). Ensure PRs strictly follow guidelines before requesting review in kenn-io/kata.

Top PR Submission Do's

  • Add unit tests with >80% coverage for modified code paths
  • Run repository linter and code formatters locally before pushing
  • Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without referencing an existing issue
  • Do not mix refactoring and feature logic into a single commit
  • Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
7 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
93.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
72.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
93.4%
Merge Gauge
72.7%
1st-Timer
Community Vibe59/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for kenn-io/kata
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/kenn-io/kata)](https://getmerged.abhishekco.de/kenn-io/kata?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for kenn-io/kata.

View all good first issues directly on GitHub

Looking for more Go beginner tasks?Explore Go GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for kenn-io/kata

When evaluating whether to contribute to kenn-io/kata, 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 kenn-io/kata acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to kenn-io/kata

01

Is kenn-io/kata welcoming to first-time open-source contributors?

kenn-io/kata has a recorded first-timer success rate of 72.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~7 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 64.4 C-Rank™ score represent?

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 64.4 places kenn-io/kata in the Welcoming tier.

04

What is the external contributor pull request merge rate for kenn-io/kata?

The external pull request merge rate is 93.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in kenn-io/kata?

kenn-io/kata does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for kenn-io/kata 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.