🎨 Powerful, minimalistic, cross-platform, opensource note-taking app
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 88%
Response Time: 3d
First Timer Success: 100%
LinwoodDev/Butterfly has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LinwoodDev/Butterfly respond to incoming external pull requests in approximately 63.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 67.1 places LinwoodDev/Butterfly in the A tier.
The external contributor pull request merge rate for LinwoodDev/Butterfly is 88.5%, based on public PR activity from non-core contributors.
LinwoodDev/Butterfly currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in LinwoodDev/Butterfly. Prompt code reviews with positive guidance for new contributors.
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/LinwoodDev/Butterfly?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 - Thursday from 09:00 to 13:00 UTC (09:00 - 13: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 ~41 hours (96% approval). Large PRs (>500 lines) take ~305 hours (40% 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 Dart.
Flutter email client for Nostr - send and receive encrypted emails using the Nostr protocol
ServerBox - server status & toolbox
Interactive user feedback tool for Flutter 🎉
What happened? When using the pen tool, lines appear when drawing, but disappear after about 2 seconds. line only renders after closing and reopening the app. Lines are still selectable with lasso tool while invisible, and persist in the file. Device: boox go 10.3 Reproduction steps: Draw a line with the stylus Lift the pen Observe line vanishes ~2 seconds later Close and reopen app Line reappears Version 2.5.3 and 2.5.2 Platform Android Relevant log output [info] | 15:18:26 679ms | App started [route] | 15:18:26 852ms | Open route named home Arguments: {} [route] | 15:18:28 394ms | Open route named new Arguments: {path: , remote: } [verbose] | 15:18:28 413ms | Changing tool to index: 0 [verbose] | 15:18:28 441ms | Baking viewport (reset: true, viewChanged: true, rendererStatesChanged: false) [verbose] | 15:18:29 970ms | Changing tool to index: 1 [verbose] | 15:18:29 970ms | Refreshing CurrentIndexCubit [bloc-event] | 15:18:31 174ms | DocumentBloc receive event: ToolsChanged [bloc-t
Is your feature request related to a problem? Please describe No response Describe your feature request! Currently, prerelease versions (beta, rc, etc.) don't include the prerelease identifier in the app's Info.plist file, which causes version comparison issues for third-party update checkers. Current behavior: GitHub Release tag: 2.5.0-beta.0 CFBundleShortVersionString in Info.plist: 2.5.0.0 ❌ CFBundleVersion in Info.plist: 164 Expected behavior: GitHub Release tag: 2.5.0-beta.0 CFBundleShortVersionString in Info.plist: 2.5.0-beta.0 ✅ CFBundleVersion in Info.plist: 164 Why this matters: When comparing versions programmatically: 2.5.0.0 (from Info.plist) > 2.5.0-beta.0 (from GitHub) ❌ Incorrect Update checkers think the local version is newer than the latest release This breaks automatic update detection Suggested fix: Include the prerelease identifier in CFBundleShortVersionString to match the semantic versioning standard: <key>CFBundleShortVersionString</key> <string>2.5.
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 LinwoodDev/Butterfly, 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 LinwoodDev/Butterfly acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.5% were successfully merged into the primary branch.
LinwoodDev/Butterfly has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 67.1 places LinwoodDev/Butterfly in the Welcoming tier.
The external pull request merge rate is 88.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LinwoodDev/Butterfly 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 LinwoodDev/Butterfly 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.