poooi/poi - Open Source PR Review Scorecard

Scalable KanColle browser and tool.

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

External PR Merge Rate: 91%

Response Time: 3d

First Timer Success: 100%

Frequently Asked Questions

Is poooi/poi welcoming to first-time open-source contributors?

poooi/poi has a recorded first-timer success rate of 100.0%. 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 poooi/poi respond to incoming external pull requests in approximately 80.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 69.5 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 69.5 places poooi/poi in the A tier.

What is the external contributor pull request merge rate for poooi/poi?

The external contributor pull request merge rate for poooi/poi is 91.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in poooi/poi?

poooi/poi currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

poooi
poooi/poiA•Welcoming1.8k
GitHub
Back to Explorer
poooi

poooi/poi

1,801
Active (30d)A•Welcoming(69/100)TypeScript

Scalable KanColle browser and tool.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in poooi/poi. Reviews community pull requests with focus on project quality.

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
3 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
91.1%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
91.1%
Merge Gauge
100.0%
1st-Timer
Community Vibe66/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

poi 版本 / poi version: 11.1.0 操作系统 / OS: Win11 24H2 Build 26100.4351 插件名和版本 / Plugin name & version: Name: poi-plugin-kcrdb Ver: 0.0.2 你遇到了什么样的问题 / The problem you've met: Unable to receive response of api_req_kousyou/remodel_slot_recover with window.addEventListener('game.response') 有没有重现的方法,或者与问题相关的任何信息 / How to reproduce, or any information that might be related: Response of api_req_kousyou/remodel_slot_recover of this screen IF success, we should see a request send to KCRDB

📅 Opened May 4, 2026💬 2 comments
Quality: 35/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 poooi/poi

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

Frequently Asked Questions - Contributing to poooi/poi

01

Is poooi/poi welcoming to first-time open-source contributors?

poooi/poi has a recorded first-timer success rate of 100.0%. 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 ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.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 69.5 places poooi/poi in the Welcoming tier.

04

What is the external contributor pull request merge rate for poooi/poi?

The external pull request merge rate is 91.1%. 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 poooi/poi?

Yes, poooi/poi currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for poooi/poi 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.