A Flash Player emulator written in Rust
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 72%
Response Time: 2d
First Timer Success: 42%
ruffle-rs/ruffle has a recorded first-timer success rate of 41.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ruffle-rs/ruffle respond to incoming external pull requests in approximately 37.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 61.0 places ruffle-rs/ruffle in the A tier.
The external contributor pull request merge rate for ruffle-rs/ruffle is 72.3%, based on public PR activity from non-core contributors.
ruffle-rs/ruffle currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in ruffle-rs/ruffle. Ensure PR scope matches issue requirements closely before requesting review.
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/ruffle-rs/ruffle?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (90% approval). Large PRs (>500 lines) take ~181 hours (33% approval). Keep your diff compact for rapid review.
Describe the bug In all of the Submachine games HD builds, the footer controls were replaced with text buttons to control fullscreen, music, and sound fx. These buttons are all implimented as via html href like the following: <A HREF="asFunction:toggle_music" TARGET="">music: on</A> When clicking on the button, Ruffle will attempt to open these functions in an external web browser instead of executing the referenced actionscript function. Expected behavior As demonstrated by the flash packaged HD builds: Clicking on the buttons in the footer should execute the referenced function, not open an external browser. Content Location Unfortunately, I can't link directly to an affected swf as this is paid content that's still up for sale. Any of the SWF builds in the release will exhibit this behavior however. https://mateuszskutnik.itch.io/submachine-collection Affected platform Desktop app Operating system Windows 11 24H2 26100.8246 Browser No response Additional information The full html
Describe the bug Using textField.restrict will disable a text input field's default behaviour of starting a new line when the Enter key is pressed. This is inconsistent with Flashplayer's behaviour. The issue seems to occur regardless of what is entered into restrict. These both trigger the bug: textField.restrict = "A-Za-z0-9" textField.restrict = "" Expected behavior Enter key should still start a new line. Content Location text bug.zip Affected platform Desktop app Operating system Windows 10 Browser No response Additional information Tested in Desktop Ruffle.
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 ruffle-rs/ruffle, 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 ruffle-rs/ruffle acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.3% were successfully merged into the primary branch.
ruffle-rs/ruffle has a recorded first-timer success rate of 41.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 61.0 places ruffle-rs/ruffle in the Welcoming tier.
The external pull request merge rate is 72.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ruffle-rs/ruffle 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 ruffle-rs/ruffle 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.