peltonapp/Pelton - Open Source PR Review Scorecard

📨 An open-source email client built around your privacy, cross-platform with zero telemetry, fully yours.

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

External PR Merge Rate: 13%

Response Time: 4d

First Timer Success: -

Frequently Asked Questions

Is peltonapp/Pelton welcoming to first-time open-source contributors?

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

What does the 46.9 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 46.9 places peltonapp/Pelton in the B tier.

What is the external contributor pull request merge rate for peltonapp/Pelton?

The external contributor pull request merge rate for peltonapp/Pelton is 12.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in peltonapp/Pelton?

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

peltonapp
peltonapp/PeltonB•Solid153
GitHub
Back to Explorer
peltonapp

peltonapp/Pelton

153
Active (30d)B•Solid(47/100)Low Sample (<20 PRs)Go

📨 An open-source email client built around your privacy, cross-platform with zero telemetry, fully yours.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.9/10
Patience Score
8.4/10
Nitpick Rate
20%

Highly welcoming maintainers in peltonapp/Pelton. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in peltonapp/Pelton focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

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

Average Response Latency

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

Merge Efficiency
12.5%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
12.5%
Merge Gauge
0.0%
1st-Timer
Community Vibe5/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Add a Brazilian Portuguese (pt-BR) locale to bring Pelton's UI translation coverage to Brazilian Portuguese speakers. Scope Add frontend/src/lib/locales/pt-BR.ts mirroring the existing locale files (en/de/fr/es/nl), translating every key. Register the locale in the i18n loader/selector so it is selectable in settings. Keys must stay in sync with the other five locales: every key present in en.ts must exist here (no key enforcement is automated, so this needs a manual pass). Notes No em-dashes in user-facing strings. Match placeholder tokens exactly ({count}, {who}, etc.); translate the surrounding text only. Keep the flat dotted key structure identical to en.ts so ordering diffs stay readable. Rationale Portuguese has around 260M speakers with a large desktop user base in Brazil; one of the highest-reach languages not yet covered.

📅 Opened Jul 25, 2026💬 3 comments
Quality: 80/100Contribute

Add a Italian (it) locale to bring Pelton's UI translation coverage to Italian speakers. Scope Add frontend/src/lib/locales/it.ts mirroring the existing locale files (en/de/fr/es/nl), translating every key. Register the locale in the i18n loader/selector so it is selectable in settings. Keys must stay in sync with the other five locales: every key present in en.ts must exist here (no key enforcement is automated, so this needs a manual pass). Notes Match placeholder tokens exactly ({count}, {who}, etc.); translate the surrounding text only. Keep the flat dotted key structure identical to en.ts so ordering diffs stay readable. Rationale Completes the core Western-European set (alongside German, French, Spanish and Dutch); roughly 65M native speakers.

📅 Opened Jul 25, 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 peltonapp/Pelton

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

Frequently Asked Questions - Contributing to peltonapp/Pelton

01

Is peltonapp/Pelton welcoming to first-time open-source contributors?

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

03

What does the 46.9 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 46.9 places peltonapp/Pelton in the Solid tier.

04

What is the external contributor pull request merge rate for peltonapp/Pelton?

The external pull request merge rate is 12.5%. 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 peltonapp/Pelton?

Yes, peltonapp/Pelton 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 peltonapp/Pelton 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.