A free AI agent & toolbox for Android | 一站式安卓 AI 智能体 & 工具箱
C-Rank Grade: B (Solid) - 56/100
External PR Merge Rate: 42%
Response Time: 30d
First Timer Success: 100%
wangzhishou/OneBox has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in wangzhishou/OneBox respond to incoming external pull requests in approximately 719.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 55.7 places wangzhishou/OneBox in the B tier.
The external contributor pull request merge rate for wangzhishou/OneBox is 42.3%, based on public PR activity from non-core contributors.
wangzhishou/OneBox currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in wangzhishou/OneBox 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/wangzhishou/OneBox?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~468 hours (53% approval). Large PRs (>500 lines) take ~3454 hours (19% approval). Keep your diff compact for rapid review.
androidCompileSdkExtension = "-" silently becomes null, hiding the intended SDK extension level Severity: Low File: gradle/libs.versions.toml:6 The version catalog declares: androidCompileSdkExtension = "-" In ConfigureKotlinAndroid.kt this is consumed as: compileSdkExtension = libs.versions.androidCompileSdkExtension.get().toIntOrNull() "-".toIntOrNull() returns null, so compileSdkExtension is silently unset. This looks like a leftover placeholder from when the project targeted a specific extension level (e.g. "13" for Android 13 Tiramisu extension). It is never overridden anywhere, so the build silently uses no extension. Why it matters If a future AGP or platform release requires a specific SDK extension level for new APIs, the build will silently fall back to the base compileSdk rather than failing loudly. The "-" value communicates no intent — it should either be removed (letting the extension stay unset explicitly) or set to the actual desired value.
"universal" ABI flavor produces identical APK to "arm64" — misleading name and wasted build time Severity: Medium File: app/build.gradle.kts:265-270 Both the arm64 and universal ABI flavors specify the exact same abiFilters — only arm64-v8a. The "universal" name conventionally implies a multi-architecture APK (e.g. arm64-v8a + armeabi-v7a + x86_64), but here it is a carbon copy: create("arm64") { dimension = "abi" ndk { abiFilters.clear() abiFilters.add("arm64-v8a") } } create("universal") { dimension = "abi" ndk { abiFilters.clear() abiFilters.add("arm64-v8a") } } The same duplication exists in build-logic/convention/src/main/kotlin/com/t8rin/imagetoolbox/ConfigureKotlinAndroid.kt for library modules and in ImageToolboxLibraryPlugin.kt. Why it matters Every CI run and local ./build_release.sh builds both variants, doubling the matrix (7 app flavors × 2 ABI = 14 APKs) while producing byte-identical native libraries. Users who
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 wangzhishou/OneBox, 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 wangzhishou/OneBox acknowledge new external contributions in approximately 29 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 42.3% were successfully merged into the primary branch.
wangzhishou/OneBox has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~29 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 55.7 places wangzhishou/OneBox in the Solid tier.
The external pull request merge rate is 42.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, wangzhishou/OneBox 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 wangzhishou/OneBox 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.