Community-built comprehensive 2D content creation appplication for graphic design, digital art, and interactive real-time motion graphics powered by a node-based procedural graphics engine
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 67%
Response Time: -
First Timer Success: 21%
GraphiteEditor/Graphite has a recorded first-timer success rate of 21.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in GraphiteEditor/Graphite 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 65.8 places GraphiteEditor/Graphite in the A tier.
The external contributor pull request merge rate for GraphiteEditor/Graphite is 67.0%, based on public PR activity from non-core contributors.
GraphiteEditor/Graphite does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in GraphiteEditor/Graphite. 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/GraphiteEditor/Graphite?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (84% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
My mouse position keeps getting tied to random properties sliders. With this bug, whenever I have properties in view, the mouse position is increasing or decreasing random values in the sliders, and I have no apparent way to cancel that or control which ones should react to the mouse position. I'm having a bit of a double clicking trouble, so some crazy interaction might be happening whenever my mouse clicks a field multiple rapid times. I'm on Google Chrome / Windows Video of the issue, since I'm not being able to upload it directly.
When the Artboard tool is selected, G/S (like the G/R/S of the Select and Path tools) needs to allow the user to grab and scale the selected artboard. Code should be reused in the implementation.
Currently, the Text node's "Align" parameter (Left/Center/Right/Justify) has no effect, and left alignment occurs regardless of the setting, when the "Max Width" setting is not active. It should use its own bounding box across all rows of text as the basis for centered and right-aligned justification.
Create a new document Draw a layer Open the node graph Double-click the layer to enter its sub-graph With no layers or nodes selected, hit CtrlD (CmdD on Mac) --> The parent graph's layer, that we are currently viewing the inside of, has unexpectedly been duplicated into its own sub-graph! capture_37_.mp4
As the title suggests.
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 GraphiteEditor/Graphite, 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 GraphiteEditor/Graphite acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.0% were successfully merged into the primary branch.
GraphiteEditor/Graphite has a recorded first-timer success rate of 21.1%. 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 65.8 places GraphiteEditor/Graphite in the Welcoming tier.
The external pull request merge rate is 67.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
GraphiteEditor/Graphite 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 GraphiteEditor/Graphite 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.