Plotly Dash components based on Mantine React Components
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 100%
Response Time: 9d
First Timer Success: 100%
snehilvj/dash-mantine-components has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in snehilvj/dash-mantine-components respond to incoming external pull requests in approximately 216.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 51.8 places snehilvj/dash-mantine-components in the B tier.
The external contributor pull request merge rate for snehilvj/dash-mantine-components is 100.0%, based on public PR activity from non-core contributors.
snehilvj/dash-mantine-components currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Plotly Dash components based on Mantine React Components
Active maintainer team in snehilvj/dash-mantine-components 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/snehilvj/dash-mantine-components?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 Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~140 hours (96% approval). Large PRs (>500 lines) take ~1037 hours (45% approval). Keep your diff compact for rapid review.
Mantine v9 Release UPDATE: Dash v4.5 now supports React 19, and work has begun on Dash Mantine Components v3.0. See below for more information and ways to contribute. Mantine v9 has been released with new features and breaking changes. This release requires React 19, which is not yet supported in Dash (see Dash issue #3231). As a result, Dash Mantine Components will remain on Mantine v8 for the v2.x series. Work on DMC v3 will begin once React 19 support is available in Dash. Important compatibility note Mantine documentation now defaults to v9. DMC is based on Mantine v8. To access the correct upstream documentation for DMC, use the Mantine v8 docs: https://v8.mantine.dev/ What’s new in Mantine v9 Mantine v9 changelog: https://github.com/mantinedev/mantine/releases Mantine migration guide: https://mantine.dev/guides/migration-guide/
Bug Description MenuItems inside a SubMenu only register their first n_click but not subsequent n_clicks. However, after clicking any main-level MenuItem in the menu, submenu items suddenly work normally and n_clicks increments on each click. Environment dash-mantine-components: 2.4.0 dash: 3.3.0 python: 3.12.0 Steps to Reproduce Click a submenu item multiple times without clicking a main menu item: n_clicks increments once for each button then stops Click a main menu item once Click submenu items again: n_clicks now increments properly (2, 3, 4...) Minimal Reproducible Example import dash_mantine_components as dmc from dash import Dash, Input, Output, html app = Dash(__name__) menu = dmc.Menu( children=[ dmc.MenuTarget(dmc.Button("Open Menu")), dmc.MenuDropdown( children=[ dmc.MenuItem("Main Item", id="main-item"), dmc.SubMenu( children=[ dmc.SubMenuTarget(dmc.SubMenuItem(
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 snehilvj/dash-mantine-components, 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 snehilvj/dash-mantine-components acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
snehilvj/dash-mantine-components has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 days+. 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 51.8 places snehilvj/dash-mantine-components in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, snehilvj/dash-mantine-components 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 snehilvj/dash-mantine-components 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.