An addon for Godot that adds a visual scripting solution, inspired by engines such as Clickteam Fusion 2.5 and Construct's event sheet editors.
C-Rank Grade: D (Risky) - 23/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
LexianDEV/FlowKit has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LexianDEV/FlowKit respond to incoming external pull requests in approximately 0.4 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 23.0 places LexianDEV/FlowKit in the D tier.
The external contributor pull request merge rate for LexianDEV/FlowKit is 0.0%, based on public PR activity from non-core contributors.
LexianDEV/FlowKit currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An addon for Godot that adds a visual scripting solution, inspired by engines such as Clickteam Fusion 2.5 and Construct's event sheet editors.
Active maintainer team in LexianDEV/FlowKit 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/LexianDEV/FlowKit?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 ~4 hours (81% approval). Large PRs (>500 lines) take ~2 hours (29% approval). Keep your diff compact for rapid review.
There are many cases where users want to group up a chunk of logic inside an Event Sheet and reuse it in multiple places without duplicating Actions. Common examples include: Moving the player Running a transition sequence Recalculating stats after a level‑up Any multi‑step sequence that appears in multiple Events Right now, FlowKit doesn’t offer a way to define reusable logic inside the visual scripting interface. Everything must be either duplicated or pushed into GDScript, which breaks the visual‑scripting workflow. If you agree that FlowKit could benefit from a built‑in mechanism for local, reusable logic, I’d like to propose Subsheets: a visual‑scripting version of local/nested functions in languages like C#, JavaScript, and Python. What Subsheets Are Subsheets would behave like Event Sheets, except... They can only be created from within the Event Sheet editor They are attached to a specific parent Event Sheet They are not global assets. They exist only as part o
A good example scene to test this functionality would be one for a quiz game. If you agree, feel free to make a Task Issue and assign it to me @Lexian-droid Originally posted by @CG-Tespy in #53
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 LexianDEV/FlowKit, 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 LexianDEV/FlowKit acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
LexianDEV/FlowKit has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 23.0 places LexianDEV/FlowKit in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LexianDEV/FlowKit currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for LexianDEV/FlowKit 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.