Companion to your Decent Espresso machine
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 68%
Response Time: 8h
First Timer Success: 83%
decentespresso/decaid has a recorded first-timer success rate of 83.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in decentespresso/decaid respond to incoming external pull requests in approximately 7.7 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 decentespresso/decaid in the A tier.
The external contributor pull request merge rate for decentespresso/decaid is 68.3%, based on public PR activity from non-core contributors.
decentespresso/decaid currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Dart project in decentespresso/decaid 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/decentespresso/decaid?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 Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (85% approval). Large PRs (>500 lines) take ~37 hours (31% approval). Keep your diff compact for rapid review.
Goal Improve desktop distribution and ensure application-managed data is stored in platform-appropriate locations rather than appearing in the user's Documents or home directory. Investigation outcome These are related release-quality concerns, but they require independent fixes: Desktop builds are currently published mainly as raw ZIP or tarball bundles and should also be distributed as conventional installers/packages. Installer format does not change the behaviour of getApplicationDocumentsDirectory(). getApplicationDocumentsDirectory() intentionally resolves to the user's Documents location. On Linux, the XDG Documents directory may be configured as $HOME; on Windows it resolves to the Documents known folder; and on macOS containment depends on the application sandbox entitlements of the shipped app, not whether it is distributed in a ZIP, DMG, or PKG. Internal application state must therefore use explicit Application Support, cache, and temporary directories. Existing installati
with InAppWebView 6.2.0 we get linux support. This means we can remove the platform check and actually show skins now. Additionally, I'd like to harden the WebUI solution when using a custom file based skin. it would make sense to copy the contents of the folder over to apps documents/skins path and set it as the default. this way users can use custom skins from the file system as well as have them persist over app restarts. Upon restart, Bridge app would check if the original path is accessible and if not, fallback to the local snapshot in the documents folder. However, right now (InAppWebView 6.2.0-beta.3), we would need to build WebKit for amd/arm64 ourselves, therefore we will wait with this until prebuilt libs are available for our build containers.
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 decentespresso/decaid, 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 decentespresso/decaid acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.3% were successfully merged into the primary branch.
decentespresso/decaid has a recorded first-timer success rate of 83.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 hours. 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 decentespresso/decaid in the Welcoming tier.
The external pull request merge rate is 68.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, decentespresso/decaid currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for decentespresso/decaid 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.