sourcebot-dev/sourcebot - Open Source PR Review Scorecard

Sourcebot is a self-hosted tool that helps humans and agents understand your codebase.

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

External PR Merge Rate: 67%

Response Time: 8d

First Timer Success: 27%

Frequently Asked Questions

Is sourcebot-dev/sourcebot welcoming to first-time open-source contributors?

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

What does the 60.2 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 60.2 places sourcebot-dev/sourcebot in the A tier.

What is the external contributor pull request merge rate for sourcebot-dev/sourcebot?

The external contributor pull request merge rate for sourcebot-dev/sourcebot is 67.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in sourcebot-dev/sourcebot?

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

sourcebot-dev
sourcebot-dev/sourcebotA•Welcoming4.0k
GitHub
Back to Explorer
sourcebot-dev

sourcebot-dev/sourcebot

3,985
Active (30d)A•Welcoming(60/100)TypeScript

Sourcebot is a self-hosted tool that helps humans and agents understand your codebase.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Mentor

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
25%

Responsive & active maintainer team in sourcebot-dev/sourcebot. Reviews pull requests with focus on project architectural goals.

Top PR Submission Do's

  • •Verify all existing package test suites run cleanly
  • •Use conventional commit messages and clean branch names
  • •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
8 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
67.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
27.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
16 core
Highly collaborative maintainer core
Diagnostic Health HUD
67.2%
Merge Gauge
27.3%
1st-Timer
Community Vibe35/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

If I navigate to a path that does not exist when in the code browser, I hit the following error message: A user could hit this when switching branches, when a file has been deleted or moved from a branch, or other scenarios. GitHub's 404 page:

📅 Opened Jan 30, 2026💬 10 comments
Quality: 15/100Contribute

Feature Description As a normal user (no longer an owner), I encountered a pop-up prompting me to 'Upgrade'. This upgrade prompt should ONLY be shown to the current owner(s) of the sourcebot instance, not to users without the owner role. Expected Behaviour: The 'Upgrade' popup should be shown exclusively to users who currently have the 'owner' role. Regular users (including former owners who no longer have the owner role) should NOT receive upgrade prompts. The system should accurately check for the 'owner' role before displaying any upgrade-related UI elements. User Story When I sign in as a normal user, I should NOT receive upgrade prompts intended for organization owners. Only current owners of the organization should see the upgrade pop-up.

📅 Opened Jan 28, 2026💬 5 comments
Quality: 30/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 sourcebot-dev/sourcebot

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

Frequently Asked Questions - Contributing to sourcebot-dev/sourcebot

01

Is sourcebot-dev/sourcebot welcoming to first-time open-source contributors?

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

03

What does the 60.2 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 60.2 places sourcebot-dev/sourcebot in the Welcoming tier.

04

What is the external contributor pull request merge rate for sourcebot-dev/sourcebot?

The external pull request merge rate is 67.2%. 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 sourcebot-dev/sourcebot?

Yes, sourcebot-dev/sourcebot currently has 2 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 sourcebot-dev/sourcebot 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.