Self-hosted family planner - tasks, calendars, shopping, meals, budget. Your data, your server.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 67%
Response Time: 12h
First Timer Success: 53%
ulsklyc/yuvomi has a recorded first-timer success rate of 52.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ulsklyc/yuvomi respond to incoming external pull requests in approximately 12.3 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 71.1 places ulsklyc/yuvomi in the S tier.
The external contributor pull request merge rate for ulsklyc/yuvomi is 67.3%, based on public PR activity from non-core contributors.
ulsklyc/yuvomi does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Self-hosted family planner - tasks, calendars, shopping, meals, budget. Your data, your server.
Strict review standards in ulsklyc/yuvomi. Ensure PR scope matches issue requirements closely before requesting review.
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/ulsklyc/yuvomi?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (85% approval). Large PRs (>500 lines) take ~115 hours (31% approval). Keep your diff compact for rapid review.
From Discussion #1226. What was promised 15 September, in the thread: "a switch per subscription that turns its reminder off is fine, and small enough to take as a PR." @torbenvanassche offered one from his fork; none has been opened so far. This is open for a contribution: what was accepted is a PR, and whoever picks it up first builds it. A comment here before starting avoids two people doing the same work. Today Every active subscription gets one reminder before its next payment. syncReminder() deletes and recreates it on every write (server/routes/subscriptions.js:46-60). reminder_days is NOT NULL with a range of 0 to 365 (server/db.js:2877). Setting it to 0 does not switch the reminder off, it moves it to the due date. A reminder that is dismissed or deleted comes back on the next edit or renewal. Switching the subscription off removes the reminder, but also its budget entry and its share of the monthly cost. Scope A switch per subscription, on by default, so existing subscript
Follow-up to #1465. Set in CSS, not looked at in a browser. What to check Since #1465 a multi-day event in the desktop month is one bar per week row. Two parts of that depend on the reading direction and were only verified left to right: Open edge of a continued bar. public/styles/calendar.css has [dir="rtl"] .cal-band__cont (around line 2076) to mirror the continuation mark; the bar itself uses logical properties. Receded tint over neighbouring-month days. .month-bands > .cal-band--outside (around line 2163) gives the segment over days of the previous or next month the same receded tint as the chips there. In LTR the colour change sits exactly on the cell boundary (measured at 1280x800). In RTL the column order flips, so the segment boundaries must flip with it. How Switch the household or the browser to an RTL locale (ar or fa), open the month at 1280x800 with a multi-day event that crosses a week row and a month edge, light and dark. Acceptance The continuation mark and the open
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 ulsklyc/yuvomi, 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 ulsklyc/yuvomi acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.3% were successfully merged into the primary branch.
ulsklyc/yuvomi has a recorded first-timer success rate of 52.6%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 hours. 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 71.1 places ulsklyc/yuvomi in the Elite tier.
The external pull request merge rate is 67.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
ulsklyc/yuvomi does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for ulsklyc/yuvomi 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.