Trezor Suite Monorepo
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 77%
Response Time: 1d
First Timer Success: 63%
trezor/trezor-suite has a recorded first-timer success rate of 63.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in trezor/trezor-suite respond to incoming external pull requests in approximately 26.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 72.3 places trezor/trezor-suite in the S tier.
The external contributor pull request merge rate for trezor/trezor-suite is 77.0%, based on public PR activity from non-core contributors.
trezor/trezor-suite currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in trezor/trezor-suite. Reviews community pull requests with focus on project quality.
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/trezor/trezor-suite?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 08:00 to 12:00 UTC (08:00 - 12: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 (35% approval). Keep your diff compact for rapid review.
Describe the bug In offline mode we show banner informing user to get online to use app without limitations. The banner is using error instead of warning intent. As user is still able to navigate the use part of the app this can't be considered error. Offline is a state, not a failure. Also, this will align the Mobile and Desktop platform. Info: Platform: desktop/web Suite Version: 26.10.0 OS: macOS Expected behavior Banner intent warning icon WifiSlash Screenshots
When long pressing (?) on any of the elements in the screenshots then the values get copied to the clipboard.
Description ETC, Sepolia and Hoodi have no caipId in networksConfig.ts, so WalletConnect cannot map a session on those chains back to a Suite account and the UI is unable to pair them. Scope Add caipId: ETC eip155:61, Ethereum Sepolia eip155:11155111, Ethereum Hoodi eip155:560048 Pairing a dApp on each chain resolves the correct account
Implement warning message in devtools console. Discussion at https://satoshilabs.slack.com/archives/CKZHV2G13/p1775834813955069
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 trezor/trezor-suite, 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 trezor/trezor-suite acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.0% were successfully merged into the primary branch.
trezor/trezor-suite has a recorded first-timer success rate of 63.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 72.3 places trezor/trezor-suite in the Elite tier.
The external pull request merge rate is 77.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, trezor/trezor-suite currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for trezor/trezor-suite 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.