Fighting global poverty with the help of everyday people and your coding skills. Public repository of the NGO and global initiative Social Income.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 83%
Response Time: 3d
First Timer Success: 87%
socialincome-san/public has a recorded first-timer success rate of 86.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in socialincome-san/public respond to incoming external pull requests in approximately 77.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 74.2 places socialincome-san/public in the S tier.
The external contributor pull request merge rate for socialincome-san/public is 83.3%, based on public PR activity from non-core contributors.
socialincome-san/public currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Fighting global poverty with the help of everyday people and your coding skills. Public repository of the NGO and global initiative Social Income.
Collaborative maintainer environment in socialincome-san/public. Reviews community pull requests with focus on project quality.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/socialincome-san/public?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~50 hours (96% approval). Large PRs (>500 lines) take ~371 hours (37% approval). Keep your diff compact for rapid review.
Remove the two visible lines in the dialog that appears when closing the donation flow. Steps to reproduce: Start a donation. Close the donation window using the X button. The dialog appears with two unwanted lines. Expected behavior: The dialog should appear without these lines.
Add a pill showing the number of candidates on each country page: The candidate count is already calculated when creating a new program (see Initiate program on the landing page), so we should be able to reuse the same logic/data:
We already send emails with SendgridMailService (#2913). After SendGrid accepts a mail, we currently keep no copy of it. Later we want a table in the Portal admin UI: when, to whom, subject, body, etc. That UI is a separate issue. This issue is only: save every sent email in the database. Split the work into 2 PRs. Merge PR 1 before starting PR 2. PR 1 — Design and add a database table Prisma is how this app talks to PostgreSQL. You do not write SQL by hand first. You describe the table in the Prisma schema, then Prisma creates the SQL migration. File: website/src/lib/database/schema.prisma Think about what the future admin table needs, then propose columns + types. At least: when the email was sent recipient(s) — this is an email address, not necessarily a User in our DB (the monthly summary goes to addresses from an env variable) subject body maybe the from-address send() already allows one or many recipients (to: string | string[]). Decide how to store that (one row per send
The pages Open Source and People shows the module Open Source Contributors. Currently, RenovateBot always appears first in the contributor list. Can we exclude this account from the list?
If a CSV has an issue the error message is very long (which is OK), but it then goes over the dialog box size and one is blocked and can't click anything. Easiest would probably be to truncating the message.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to socialincome-san/public, 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 socialincome-san/public acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
socialincome-san/public has a recorded first-timer success rate of 86.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 74.2 places socialincome-san/public in the Elite tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, socialincome-san/public currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for socialincome-san/public 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.