sspanak/tt9 - Open Source PR Review Scorecard

A T9 keyboard for Android inspired by the classic Nokia phones of the 2000s.

C-Rank Grade: A (Welcoming) - 61/100

External PR Merge Rate: 89%

Response Time: 3d

First Timer Success: 50%

Frequently Asked Questions

Is sspanak/tt9 welcoming to first-time open-source contributors?

sspanak/tt9 has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in sspanak/tt9 respond to incoming external pull requests in approximately 65.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 61.1 C-Rank™ score (A Tier) represent?

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 61.1 places sspanak/tt9 in the A tier.

What is the external contributor pull request merge rate for sspanak/tt9?

The external contributor pull request merge rate for sspanak/tt9 is 89.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in sspanak/tt9?

sspanak/tt9 currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

sspanak
sspanak/tt9A•Welcoming510
GitHub
Back to Explorer
sspanak

sspanak/tt9

510
InactiveA•Welcoming(61/100)Java

A T9 keyboard for Android inspired by the classic Nokia phones of the 2000s.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.6/10
Patience Score
8.6/10
Nitpick Rate
35%

Highly welcoming maintainers in sspanak/tt9. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
89.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
12 core
Highly collaborative maintainer core
Diagnostic Health HUD
89.4%
Merge Gauge
50.0%
1st-Timer
Community Vibe51/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for sspanak/tt9
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/sspanak/tt9)](https://getmerged.abhishekco.de/sspanak/tt9?utm_source=github&utm_medium=badge)

Active Good First Issues (4)

View on GitHub

Can you build the release APK from a fresh clone of the repo checked out at the tagged commit? Else, if you build from a tarball or whatever META-INF/version-control-info.textproto 1c1,5 < generate_error_reason: NO_VALID_GIT_FOUND --- > repositories { > system: GIT > local_root_path: "$PROJECT_DIR" > revision: "0fe69b5c32868803861bf3bff38a7c8fff978236" > }

📅 Opened Aug 10, 2026💬 14 comments
Quality: 65/100Contribute

As per the title. Sometimes I am typing and the backspace activates on its own and starts deleting everything. Only way to stop it is to press the backspace key a couple of times. Any way to prevent this? Seems to be random

📅 Opened Aug 5, 2026💬 6 comments
Quality: 65/100Contribute

First of all, thanks for this awesome app, it is been a joy to use so far :) I don't know how to reproduce it, but there is a bug which is quite annoying where the keyboard just stays indefinitely on the screen, and it's impossible to make it go away, except by rebooting the phone. Or killing the app, which is not that easy because the keyboard actually hides the button for that 😭 and when focusing a text field, a new keyboard pops up, but the old one is still there (can see it by resizing the new one) Here are the latest logs, if that may help: tt9-logs-1784272794536.txt

📅 Opened Jul 17, 2026💬 2 comments
Quality: 80/100Contribute

Easiest steps to reproduce (on stock Android launcher): Swipe up from home screen Make sure there is no cursor in the search field Start typing an app's name I realize this might be more of a system issue than a bug in the app, because it only gets activated after the initial digit is entered. If this can't be fixed reasonably, would a system fix be possible (I am a ROM developer).

📅 Opened Mar 17, 2026💬 12 comments
Quality: 45/100Contribute
Looking for more Java beginner tasks?Explore Java GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for sspanak/tt9

When evaluating whether to contribute to sspanak/tt9, 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 sspanak/tt9 acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to sspanak/tt9

01

Is sspanak/tt9 welcoming to first-time open-source contributors?

sspanak/tt9 has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 61.1 C-Rank™ score represent?

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 61.1 places sspanak/tt9 in the Welcoming tier.

04

What is the external contributor pull request merge rate for sspanak/tt9?

The external pull request merge rate is 89.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in sspanak/tt9?

Yes, sspanak/tt9 currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for sspanak/tt9 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.