redimp/otterwiki - Open Source PR Review Scorecard

A minimalistic wiki powered by python, markdown and git.

C-Rank Grade: B (Solid) - 54/100

External PR Merge Rate: 66%

Response Time: 21h

First Timer Success: 75%

Frequently Asked Questions

Is redimp/otterwiki welcoming to first-time open-source contributors?

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

What does the 53.8 C-Rank™ score (B 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 53.8 places redimp/otterwiki in the B tier.

What is the external contributor pull request merge rate for redimp/otterwiki?

The external contributor pull request merge rate for redimp/otterwiki is 66.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in redimp/otterwiki?

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

redimp
redimp/otterwikiBSolid1.5k
GitHub
Back to Explorer
redimp

redimp/otterwiki

1,491
BSolid(54/100)Python

A minimalistic wiki powered by python, markdown and git.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.4/10
Patience Score
7.8/10
Nitpick Rate
33%

Balanced & professional review environment in redimp/otterwiki. Maintains strict focus on technical quality and test standards.

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
21 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
66.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
19 core
Highly collaborative maintainer core
Diagnostic Health HUD
66.1%
Merge Gauge
75.0%
1st-Timer
Community Vibe63/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

I tried the Ctrl+Shift+X and it did change the text direction but didn't apply in the preview or after save.

📅 Opened Jan 27, 2026💬 1 comment
Quality: 55/100Contribute
Looking for more Python beginner tasks?Explore Python 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 redimp/otterwiki

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

Frequently Asked Questions - Contributing to redimp/otterwiki

01

Is redimp/otterwiki welcoming to first-time open-source contributors?

redimp/otterwiki has a recorded first-timer success rate of 75.0%. Repositories ranked Solid 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 ~21 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 53.8 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 53.8 places redimp/otterwiki in the Solid tier.

04

What is the external contributor pull request merge rate for redimp/otterwiki?

The external pull request merge rate is 66.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 redimp/otterwiki?

Yes, redimp/otterwiki 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 redimp/otterwiki 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.