A basic app to track your car's maintenance. Open source for Hacktoberfest 2025. Beginners are welcome!
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 50%
Response Time: 1h
First Timer Success: -
mikaelacaron/Basic-Car-Maintenance 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.
Maintainers in mikaelacaron/Basic-Car-Maintenance respond to incoming external pull requests in approximately 1.1 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 49.7 places mikaelacaron/Basic-Car-Maintenance in the B tier.
The external contributor pull request merge rate for mikaelacaron/Basic-Car-Maintenance is 50.0%, based on public PR activity from non-core contributors.
mikaelacaron/Basic-Car-Maintenance currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Swift project in mikaelacaron/Basic-Car-Maintenance welcoming community pull requests and bug fixes.
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/mikaelacaron/Basic-Car-Maintenance?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (62% approval). Large PRs (>500 lines) take ~5 hours (22% approval). Keep your diff compact for rapid review.
Describe the bug OdometerView doesn't update after the update sheet is dismissed, when updating a value To Reproduce Steps to reproduce the behavior: Go to OdometerView Swipe left to edit a reading Update the values, and tap check When that view is dismissed, it doesn't update the value Expected behavior The view shows the new updated values Screenshots N/A Device Info (please complete the following information): Device: iPhone Air OS: 26.5 App Version: N/a Additional Context this is for both the reading value and the date, they don't show the updated numbers Make sure the graph updates too
Describe the feature you want the app to have that it currently doesn't Write new unit tests for DashboardViewModel, and possibly also do some research about if there's anything extra needed when using the Firebase emulator and unit tests Describe alternatives you've considered N/A Additional context This change should be less than 300 lines of code, so it's not modifying the whole architecture to make it testable, that's very difficult and causes issues and conflicts for others, instead look for something that can be unit tested in the app right now
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 mikaelacaron/Basic-Car-Maintenance, 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 mikaelacaron/Basic-Car-Maintenance acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
mikaelacaron/Basic-Car-Maintenance 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.
The initial maintainer response time averages ~1 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 49.7 places mikaelacaron/Basic-Car-Maintenance in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mikaelacaron/Basic-Car-Maintenance currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for mikaelacaron/Basic-Car-Maintenance 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.