Get tasks and ideas out of your head. A free GTD to-do app for desktop and mobile. Works offline, no account needed
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 83%
Response Time: -
First Timer Success: 100%
dongdongbh/Mindwtr 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 dongdongbh/Mindwtr 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 63.2 places dongdongbh/Mindwtr in the A tier.
The external contributor pull request merge rate for dongdongbh/Mindwtr is 82.9%, based on public PR activity from non-core contributors.
dongdongbh/Mindwtr does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Get tasks and ideas out of your head. A free GTD to-do app for desktop and mobile. Works offline, no account needed
Highly welcoming maintainers in dongdongbh/Mindwtr. 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/dongdongbh/Mindwtr?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Tracking issue for a community-contributed encryption-at-rest feature for the blob-store sync backends. The reference design is the spec converged in discussion #1001 — Encryption at rest, Version 4 by @ltguillaume — refined over several review rounds there. Read that spec and the surrounding thread first; this issue exists so the work has a stable anchor. Scope Client-side encryption of the synced artifacts (data file, .bak, snapshots, attachments) for the backends that treat the remote as an opaque blob store: File Sync, WebDAV, Dropbox. Out of scope: mindwtr-cloud (merges server-side on PUT /v1/data, so opaque ciphertext is a redesign) and iCloud/CloudKit. Local at-rest encryption of the app's own database is also out of scope — that remains answered by OS/device encryption. Design summary (details in the spec) One home in Settings > Sync > Encryption: enable + passphrase (with confirm), Diceware generator from the EFF wordlist, passphrase change re-encrypts everything in the
Reported via email feedback (2026-08-10): On Linux Mint 22.3 (Cinnamon) with the 1.1.6 AppImage, the Mindwtr system tray icon renders as a blank space / black square in the panel's tray area. The app itself runs normally; only the tray icon is blank. Screenshot from the reporter shows an empty slot between two neighbouring tray icons in the bottom-right panel area. To investigate: Cinnamon renders tray icons via XApp/AppIndicator; likely an icon pixmap/theme-path issue specific to the AppImage packaging (the icon may be referenced by name/path that does not resolve inside the AppImage mount). Check whether deb/rpm/Flatpak on Cinnamon show the same blank icon, and whether #937's transparent-logo rework changed the tray asset.
Tracking issue for the long-term fix behind #766. Why The mobile app runs UI, SQLite access, and the whole sync cycle on the single React Native JS thread, and all data crosses the bridge. Desktop keeps storage in the native (Rust) process — a full-library read costs ~50 ms and a sync cycle never steals time from the UI. The phone pays seconds for the same read, and when the JS thread is busy every awaited SQL statement inflates with it. Numbers from the #766 beta logs at ~1,650 tasks on a mid-range Android phone: Full SQLite read: 0.5–3.2 s (desktop: ~50 ms) Sync cycle end to end: 23–32 s BEGIN taking up to 16 s with busy_timeout=5000 — the JS thread, not SQLite, is the bottleneck Taps during a cycle: 5–6 s to respond The release-by-release cost cutting (incremental saves, widget memoization, refresh-from-memory, cycle pacing) keeps improving symptoms, but the ceiling is architectural: as long as merge, serialization, and SQL share the UI thread, a large enough library wil
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 dongdongbh/Mindwtr, 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 dongdongbh/Mindwtr acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.9% were successfully merged into the primary branch.
dongdongbh/Mindwtr 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 ~-. 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 63.2 places dongdongbh/Mindwtr in the Welcoming tier.
The external pull request merge rate is 82.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
dongdongbh/Mindwtr 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 dongdongbh/Mindwtr 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.