The complete open source platform to run your entire marketplace. Storefront, vendor panel, admin console, and integrations in one enterprise-grade platform you own.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 83%
Response Time: -
First Timer Success: 50%
mercurjs/mercur has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mercurjs/mercur 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 58.7 places mercurjs/mercur in the A tier.
The external contributor pull request merge rate for mercurjs/mercur is 83.1%, based on public PR activity from non-core contributors.
mercurjs/mercur does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
The complete open source platform to run your entire marketplace. Storefront, vendor panel, admin console, and integrations in one enterprise-grade platform you own.
Active TypeScript repository in mercurjs/mercur with ongoing community development and issue triage.
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/mercurjs/mercur?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Context Mercur 2.2.0 marketplaces using Medusa 2.17.2's Stripe provider with capture: false authorize one shared PaymentIntent and create the order group / seller child orders through Mercur's POST /store/carts/:id/complete workflow. The Medusa Stripe provider maps payment_intent.amount_capturable_updated to an AUTHORIZED webhook action. That event is emitted as soon as a manual-capture PaymentIntent becomes capturable, which can be before the storefront has completed the Mercur cart into its split orders. Problem Enabling payment_intent.amount_capturable_updated on /hooks/payment/stripe_stripe can therefore introduce an authorization/completion path before Mercur's split-order completion is safely established. The Mercur Stripe documentation does not currently make the safe event set or this event-specific exception explicit enough for operators. There is a related reconciliation ambiguity: charge.refunded may update customer-payment state, but the installed Medusa Stripe provider doe
Summary The Algolia registry block (packages/registry/src/algolia) defines and listens for five "intermediate" events, but nothing in the repo emits any of them. All five subscribers are dead code, so after a product is first indexed, changes to its stock, stock location, fulfillment set, service zone, or shipping option never refresh the Algolia record — including the derived supported_countries / stock-location data that subscribers/utils/algolia-product.ts computes. The five orphaned events Defined in modules/algolia/types.ts, consumed by subscribers, emitted nowhere: Event Listening subscriber algolia.intermediate.inventory_item.changed algolia-inventory-item-changed.ts algolia.intermediate.stock_location.changed algolia-stock-location-changed.ts algolia.intermediate.fulfillment_set.changed algolia-fulfillment-set-changed.ts algolia.intermediate.service_zone.changed algolia-service-zone-changed.ts algolia.intermediate.shipping_option.changed algolia-shipping-option
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 mercurjs/mercur, 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 mercurjs/mercur acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.1% were successfully merged into the primary branch.
mercurjs/mercur has a recorded first-timer success rate of 50.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 58.7 places mercurjs/mercur in the Welcoming tier.
The external pull request merge rate is 83.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
mercurjs/mercur 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 mercurjs/mercur 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.