Kocoro-lab/Kocoro - Open Source PR Review Scorecard

A Mac-native AI agent with memory, local computer access, browser control, IM channels, and MCP-native integrations. Built on Shannon.

C-Rank Grade: S (Elite) - 72/100

External PR Merge Rate: 94%

Response Time: 21h

First Timer Success: 80%

Frequently Asked Questions

Is Kocoro-lab/Kocoro welcoming to first-time open-source contributors?

Kocoro-lab/Kocoro has a recorded first-timer success rate of 80.0%. Repositories ranked S 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 Kocoro-lab/Kocoro respond to incoming external pull requests in approximately 20.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 71.5 C-Rank™ score (S 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 71.5 places Kocoro-lab/Kocoro in the S tier.

What is the external contributor pull request merge rate for Kocoro-lab/Kocoro?

The external contributor pull request merge rate for Kocoro-lab/Kocoro is 93.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Kocoro-lab/Kocoro?

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

Kocoro-lab
Kocoro-lab/KocoroSElite403
GitHub
Back to Explorer
Kocoro-lab

Kocoro-lab/Kocoro

403
SElite(72/100)Go

A Mac-native AI agent with memory, local computer access, browser control, IM channels, and MCP-native integrations. Built on Shannon.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.7/10
Patience Score
8.0/10
Nitpick Rate
50%

Strict review standards in Kocoro-lab/Kocoro. Ensure PR scope matches issue requirements closely before requesting review.

Top PR Submission Do's

  • Ensure code complies with the project coding style
  • Keep PRs scoped to a single concern
  • Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • Do not submit PRs without linking an issue
  • Do not break existing tests without fixing them
  • Do not mix unrelated refactors in a single PR
Response Velocity
20 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
93.6%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
93.6%
Merge Gauge
80.0%
1st-Timer
Community Vibe76/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for Kocoro-lab/Kocoro.

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 Kocoro-lab/Kocoro

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

Frequently Asked Questions - Contributing to Kocoro-lab/Kocoro

01

Is Kocoro-lab/Kocoro welcoming to first-time open-source contributors?

Kocoro-lab/Kocoro has a recorded first-timer success rate of 80.0%. Repositories ranked Elite 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 ~20 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.5 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 71.5 places Kocoro-lab/Kocoro in the Elite tier.

04

What is the external contributor pull request merge rate for Kocoro-lab/Kocoro?

The external pull request merge rate is 93.6%. 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 Kocoro-lab/Kocoro?

Kocoro-lab/Kocoro 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 Kocoro-lab/Kocoro 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.