AI-first open source operating system for various devices, based on the Android.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 88%
Response Time: <1h
First Timer Success: 100%
secondly-com/OpenPhone 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 secondly-com/OpenPhone respond to incoming external pull requests in approximately 0.3 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 56.0 places secondly-com/OpenPhone in the A tier.
The external contributor pull request merge rate for secondly-com/OpenPhone is 87.9%, based on public PR activity from non-core contributors.
secondly-com/OpenPhone currently has 22 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in secondly-com/OpenPhone. Reviews community pull requests with focus on project quality.
Discussions in secondly-com/OpenPhone focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/secondly-com/OpenPhone?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~1 hours (40% approval). Keep your diff compact for rapid review.
The repo has no CODE_OF_CONDUCT.md. GitHub's community-profile checklist flags this, and outside contributors read its absence as a signal. Ask Adopt the Contributor Covenant v2.1 (or similar). Place at CODE_OF_CONDUCT.md and reference it from .github/CONTRIBUTING.md and README.md. Ideal good first issue. Size: S
Today, trying OpenPhone requires a full AOSP build (64GB RAM, ~700GB disk). Anyone without that hardware bar can't even boot the OS locally. This is the single biggest onboarding friction the project faces. Ask Publish sdk-repo-*-system-images.zip (both arm64 and x86_64) as assets on GitHub Releases, alongside SHA256 checksums that scripts/verify-prebuilt-emulator-image.sh (already exists) can consume. Impact docs/quickstart.md becomes truly "quick" (minutes, not hours). Contributor onboarding for the assistant, docs, integrations, and schemas becomes practical without a build host. Bug reports get a common reproducible baseline. Related: existing run-emulator-smoke.sh proves the emulator flow works end-to-end; this issue is about making the artifact publicly consumable. Size: M
There is no documented procedure for bumping the LineageOS base (e.g. 23.2 → 24). First things to break: PhoneWindowManager (patches 0018/0019 — LineageOS itself patches this heavily), SystemUIModule (Dagger churn), hidden ScreenCaptureInternal API (patch 0009), Darwin host-build patches in build_soong. Deliverable Add docs/LINEAGE_BUMP.md covering: Pinning: how to advance LINEAGE_BRANCH in scripts/sync.sh and manifests/openphone.xml. Known-fragile patches with links (0018/0019, 0011, 0009, 0010, host-build patches). Hidden-API audit checklist for frameworks_base changes (unstable internal APIs to re-verify). Sepolicy/service registration re-check. What to smoke-test on the emulator lab before shipping the bump. Size: S
The ~30k LOC assistant Java (overlay/packages/apps/OpenPhoneAssistant/) has zero unit tests. scripts/check-assistant-java.sh only javac-compiles it against stubs. Highest-value initial targets (pure, framework-light) policy/PolicyEngine agent/ActionExecution.capabilityFromAction (see #65) OpenAiResponsesAgentAdapter.parseDecision ToolCatalog watchers normalized-delivery / template rendering looksLikeSmsAddress, smsSelection Approach Add a JUnit 4/5 harness under overlay/packages/apps/OpenPhoneAssistant/tests/ with a minimal stubbed Android runtime (Robolectric optional; start without it). Wire it into scripts/check-assistant-java.sh so CI runs the tests. Land the first 5–10 tests on the pure classes above. Great help wanted for someone familiar with Android/Java testing. Size: M
Several fields in the agent run loop are shared across UI, agent, and overlay threads without synchronization. Findings mAgentRunGeneration — non-volatile int, written on the UI thread and read from the agent thread in isCancelled(). AssistantActivityBackend.java:216, 3291. Pending-confirmation state (mPendingActionId, related fields) — shared across UI thread, static overlay entry (:100), and agent threads with no synchronization. :3352. OpenPhoneAgentJobScheduler.isCancelled() hardcodes false (:142-144) — background jobs cannot be stopped once started. Fix Convert mAgentRunGeneration to AtomicInteger (or make it volatile + never increment across threads). Guard pending-confirmation fields with a single lock or move them into an immutable snapshot object swapped via an AtomicReference. Wire OpenPhoneAgentJobScheduler.isCancelled() to a real cancellation signal from the job manager. Small, focused change — good good first issue for someone comfortable with Java concurrency.
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 secondly-com/OpenPhone, 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 secondly-com/OpenPhone acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.9% were successfully merged into the primary branch.
secondly-com/OpenPhone 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 ~<1 hour. 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 56.0 places secondly-com/OpenPhone in the Welcoming tier.
The external pull request merge rate is 87.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, secondly-com/OpenPhone currently has 22 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for secondly-com/OpenPhone 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.