MIT-licensed Qt bindings for Go
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 75%
Response Time: 5d
First Timer Success: 75%
mappu/miqt has a recorded first-timer success rate of 75.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mappu/miqt respond to incoming external pull requests in approximately 124.8 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 52.7 places mappu/miqt in the B tier.
The external contributor pull request merge rate for mappu/miqt is 75.0%, based on public PR activity from non-core contributors.
mappu/miqt currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in mappu/miqt.
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/mappu/miqt?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~81 hours (94% approval). Large PRs (>500 lines) take ~599 hours (34% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
Examples for Hertz.
Utility that provides an API platform for validating, querying and managing BOM data
ECS server traffic guard and automation console
When using QWebEngineView and building for windows I get: [>]$ miqt-docker win64-qt6-static -windows-build --tags=windowsqtstatic 2026/04/23 02:07:36 Selecting dockerfile: win64-cross-go1.26-qt6.5-static.Dockerfile # github.com/mappu/miqt/qt6/webchannel # [pkg-config --cflags -- Qt6WebChannel] Package Qt6WebChannel was not found in the pkg-config search path. Perhaps you should add the directory containing `Qt6WebChannel.pc' to the PKG_CONFIG_PATH environment variable Package 'Qt6WebChannel', required by 'virtual:world', not found # github.com/mappu/miqt/qt6/printsupport # [pkg-config --cflags -- Qt6PrintSupport] Package Qt6PrintSupport was not found in the pkg-config search path. Perhaps you should add the directory containing `Qt6PrintSupport.pc' to the PKG_CONFIG_PATH environment variable Package 'Qt6PrintSupport', required by 'virtual:world', not found # github.com/mappu/miqt/qt6/network # [pkg-config --cflags -- Qt6Network] Package Qt6Network was not found in the pkg-config sea
miqt-uic -qt6 errors after compilation: These warnings: /* miqt-uic: no handler for leFilterPing property 'minimumSize' / / miqt-uic: no handler for leFilterPing property 'maximumSize' */ le***** means QLineEdit (but it doesn't work with other widgets either) These errors: undefined: qt.AlignmentFlag__AlignRight undefined: qt.AlignmentFlag__AlignTrailing undefined: qt.AlignmentFlag__AlignVCenter undefined: qt.AlignmentFlag__AlignRight undefined: qt.LayoutDirection__LeftToRight undefined: qt.TextFormat__AutoText .ui file below untitled.zip Im using latest version of MSYS2 with latest version of miqt (qt6 dynamic)
While working on a more complex UI design that uses horizontal spacers, I'm finding that miqt-uic does not marshal them correctly, and instead adds the following line to the generated Go code: /* miqt-uic: no handler for spacer */ This in turn, breaks the layout of the interface.
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 mappu/miqt, 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 mappu/miqt acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
mappu/miqt has a recorded first-timer success rate of 75.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 52.7 places mappu/miqt in the Solid tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mappu/miqt 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 mappu/miqt 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.