gopherium/AlphOne - Open Source PR Review Scorecard

A plugin-first CRM gone Go

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

External PR Merge Rate: 96%

Response Time: 8d

First Timer Success: 100%

Frequently Asked Questions

Is gopherium/AlphOne welcoming to first-time open-source contributors?

gopherium/AlphOne 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 gopherium/AlphOne respond to incoming external pull requests in approximately 193.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 59.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 59.5 places gopherium/AlphOne in the A tier.

What is the external contributor pull request merge rate for gopherium/AlphOne?

The external contributor pull request merge rate for gopherium/AlphOne is 96.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in gopherium/AlphOne?

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

gopherium
gopherium/AlphOneA•Welcoming180
GitHub
Back to Explorer
gopherium

gopherium/AlphOne

180
InactiveA•Welcoming(60/100)Go

A plugin-first CRM gone Go

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

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

Growing Go project in gopherium/AlphOne welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with Go style conventions
  • •Keep PRs scoped and well-documented
  • •Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
  • •Do not mix unrelated refactors with feature work
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
96.3%
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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
96.3%
Merge Gauge
100.0%
1st-Timer
Community Vibe69/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Current state: Every signed-in account opens /users and /users/new, and the menu shows Users to all of them. Without manage_users the screen hides New user, the row actions, the selection boxes and the item count, but the account list stays readable. The role column, the role filter and the Change role dialog read a role as its stored name with the first letter upper-cased, so admin reads "Admin" and member reads "Member" in every language, and neither word is in the catalog. The New user screen asks only for an email and a name, so every invitation starts as a member, although the invite mutation already takes a role and turns down one beyond the inviter's reach. A role the server does not know reads "That role is not one this deployment names.". Proposal: Only an account holding manage_users opens /users and /users/new. Any other account is sent home, and the menu hides Users from it. The users query stays as it is, so an API token with the users read scope still lists accounts. The

📅 Opened Oct 8, 2026💬 0 comments
Quality: 90/100Contribute
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 gopherium/AlphOne

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

Frequently Asked Questions - Contributing to gopherium/AlphOne

01

Is gopherium/AlphOne welcoming to first-time open-source contributors?

gopherium/AlphOne 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 ~8 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 59.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 59.5 places gopherium/AlphOne in the Welcoming tier.

04

What is the external contributor pull request merge rate for gopherium/AlphOne?

The external pull request merge rate is 96.3%. 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 gopherium/AlphOne?

Yes, gopherium/AlphOne 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 gopherium/AlphOne 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.