Simple GTK Paint Program
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 74%
Response Time: 19h
First Timer Success: 70%
PintaProject/Pinta has a recorded first-timer success rate of 70.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PintaProject/Pinta respond to incoming external pull requests in approximately 18.5 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 61.7 places PintaProject/Pinta in the A tier.
The external contributor pull request merge rate for PintaProject/Pinta is 73.8%, based on public PR activity from non-core contributors.
PintaProject/Pinta currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in PintaProject/Pinta. Maintains strict focus on technical quality and test standards.
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/PintaProject/Pinta?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 10:00 to 14:00 UTC (10:00 - 14: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 ~12 hours (92% approval). Large PRs (>500 lines) take ~89 hours (33% 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 C#.
SonarScanner for .NET
Out-of-process .NET SDK for the Durable Task Framework
A server software for ArcheAge written in .Net C#
Just have something with transparency, select it including the transparency, put the first handle higher, it will get a white background. You can circumvent it by using the wand for selection, but this makes ugly edges for semi-transparent pixels. Curve Luminousity tool should be able to turn black in white, not transparent to opague. If someone wanted to apply Curve to Alpha, that can be optional. OS: 26.1, Pinta: 3.2 beta
When I try to record an image, Pinta suggest me 2 times the PNG format. Windows 11 Pinta 3.1.2
As suggested for the axonometric grid in PR #2028: I thought about limiting the range of the angle widget. My thoughts were: Adding a NumberRange<int>? property to it, with all necessary checks, allowing us to limit the range. Fill the unavailable portion of the 'pie' with a different color I didn't do it in this pull request because I think it's already long enough and it might be better left to a separate pull request
Description When you click a 0x0 area, it should remove the current selection. If you're zoomed in, a 0x0 selection is created instead. To Reproduce Open Pinta Activate the Selection tool Zoom in such that an image pixel occupies more than 1 screen-space pixel Click on the canvas Additional Info Selection.webm Version Latest git
Description Incorrect resizing of toolbar when resizing window To Reproduce Select some tool with many options in toolbar (such as Line/Curve) Make window somewhat smaller Observe the toolbar is messed up (almost out of visible area) Additional Info 2026-01-09_23.16.01_pinta.mp4 Version Pinta 3.1.1, Linux Mint Cinnamon 22.2
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 PintaProject/Pinta, 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 PintaProject/Pinta acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.8% were successfully merged into the primary branch.
PintaProject/Pinta has a recorded first-timer success rate of 70.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 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 61.7 places PintaProject/Pinta in the Welcoming tier.
The external pull request merge rate is 73.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PintaProject/Pinta currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PintaProject/Pinta 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.