Connect suppliers, distributors and consumers to trade local produce.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 46%
Response Time: -
First Timer Success: 75%
openfoodfoundation/openfoodnetwork has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openfoodfoundation/openfoodnetwork 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 66.7 places openfoodfoundation/openfoodnetwork in the A tier.
The external contributor pull request merge rate for openfoodfoundation/openfoodnetwork is 46.3%, based on public PR activity from non-core contributors.
openfoodfoundation/openfoodnetwork currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in openfoodfoundation/openfoodnetwork 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/openfoodfoundation/openfoodnetwork?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (58% approval). Large PRs (>500 lines) take ~115 hours (21% approval). Keep your diff compact for rapid review.
Description When updating images on enterprise settings panel, when an incorrect media file is uploaded, the message error is displayed, but the file is still recorded It is linked to the PR #14552 Expected Behavior Incorrect media files should not be recorded Steps to Reproduce Go to Enterprise Settings Panel, and choose the IMAGES section Upload an incorrect file (.pdf or .doc for example) for the logo or promo image Errors are displayed, but the file is recorded, the "Remove image" button is displayed. Severity bug-s4: it's annoying, but you can use it
Description After a successful order, the page that displays the order overflows on mobile, making it harder to read the content. Expected Behavior Should not overflow, just adjust to the screen size and scroll only vertically. Actual Behaviour Overflowing a few pixels. Steps to Reproduce Example available here. Open on mobile or adjust via browser dev tools You can try manually replicating this as a guest checkout in https://staging.openfoodnetwork.org.au/ . Magic Farm allows for it. Add products to cart Go through checkout flow selecting cash and pickup Complete order Load Confirmed Order page Animated Gif/Screenshot Brave on desktop with screen set to 360px Chrome on desktop with screen set to 360px - works better (at least desktop) but still has some issues with the footer Vanadium on mobile Severity bug-s4: it's annoying, but you can use it Your Environment Operating System and version (desktop or mobile): MacOS 15.7.3 on desktop and GrapheneOS on mobile
Description Follow-up from #13261 which you can have a look at to replicate the solution Orders should not change once they are created, so if a shopper buys "Pasta!" and the producer decides the new name is "Pasta!renewed", the order content should never change and remain what the shopper has chosen. Expected Behavior Orders content should not change: they should display line items, not products. Actual Behaviour Orders are showing the new product name. Steps to Reproduce Place an order for a product Edit the name of the product in admin/products See that the name has changed in admin/orders/ORDERNUMBER/edit and /orders/ORDERNUMBER Animated Gif/Screenshot Workaround Hopefully this is rare and/or users know they have changed the name. Severity bug-s3: a feature is broken but there is a workaround
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 openfoodfoundation/openfoodnetwork, 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 openfoodfoundation/openfoodnetwork acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 46.3% were successfully merged into the primary branch.
openfoodfoundation/openfoodnetwork has a recorded first-timer success rate of 75.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 66.7 places openfoodfoundation/openfoodnetwork in the Welcoming tier.
The external pull request merge rate is 46.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openfoodfoundation/openfoodnetwork currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for openfoodfoundation/openfoodnetwork 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.