Free, open-source church management software for people, families, groups, events, attendance, giving, volunteers, and more. No subscription. Your data is yours.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 63%
Response Time: -
First Timer Success: 60%
ChurchCRM/CRM has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ChurchCRM/CRM respond to incoming external pull requests in approximately 0.0 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 64.9 places ChurchCRM/CRM in the A tier.
The external contributor pull request merge rate for ChurchCRM/CRM is 63.3%, based on public PR activity from non-core contributors.
ChurchCRM/CRM currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in ChurchCRM/CRM. Prompt code reviews with positive guidance for new contributors.
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/ChurchCRM/CRM?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (79% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
What happens On Admin → Users → (a user) → Change Password, type a password in New Password, leave Confirm New Password blank or type something else, and click Save. The page says Password Change Successful. The user's password is now whatever was in the first box, so a typo there goes unnoticed and the user cannot sign in. The self-service form (/v2/user/current/changepassword, which also serves the forced first-login change, and /portal/profile/password) does not read the confirmation box on the server either. Expected The password is not changed, and the form says "You must enter the same password in both boxes". Steps to reproduce Sign in as an administrator and open Admin → Users. Open a user's Change Password. Type NewPassword1 in New Password, leave Confirm New Password blank, and click Save. The page says Password Change Successful. The user can now sign in with NewPassword1. Cause adminChangeUserPassword() in src/admin/routes/system.php and PortalAccountPages::apply
Summary In the Family Editor (add mode) the Country dropdown has no blank option. When neither sDefaultCountry nor sChurchCountry is set, the first country in the list (Afghanistan) is pre-selected, so a new family is saved with a country nobody chose. Steps Clear Default Country (People Settings > New Record Defaults) and the church country. Open Add Family. Country shows Afghanistan. Expected A blank or "select a country" choice, so the address is saved without a country. That also keeps geocoding honest: the US Census provider is only asked when a country resolves to the US. Notes #10276 added the church-address fallback (AddressDefaults), so this only happens when both are blank. Selection is built in DropdownManager.js from data-system-default; the Person editor uses the same dropdown. Acceptance A blank first option when no default resolves, and a Cypress case that checks it.
What happened? Mailing labels cannot be generated from the Cart any more, and the underlying label report prints nothing for people whose address is recorded on the family. 1. The Cart page has no "Generate Labels" button. The pre-v2 CartView.php had a "Go To Labels" button that opened a "Generate Labels" form (label type, font, grouping, bulk-mail presort, "to the parents of", start row/column, ignore incomplete addresses, PDF/CSV). When the cart was moved to /v2/cart in #4377 (July 2018) the Tags, Map, Email and Directory buttons were carried over but the labels form was not. The template src/v2/templates/cart/generateLabels.php still exists but nothing renders it, and nothing in the app links to Reports/PDFLabel.php. #5083 reported this in 2019 and was auto-closed as stale. 2. Reports/PDFLabel.php ignores the family address. Since 0190da3 ("Remove family/person data inheritance feature") GenerateLabels() reads only per_Address1/2, per_City, per_State, per_Zip. The migration that cop
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 ChurchCRM/CRM, 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 ChurchCRM/CRM acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.3% were successfully merged into the primary branch.
ChurchCRM/CRM has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 64.9 places ChurchCRM/CRM in the Welcoming tier.
The external pull request merge rate is 63.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ChurchCRM/CRM currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ChurchCRM/CRM 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.