Karanjot786/TermUI - Open Source PR Review Scorecard

TermUI is a TypeScript/JavaScript framework for building terminal apps. Flexbox layout, JSX, hooks, global state, theming, animations, routing, and hot reload. No native dependencies.

C-Rank Grade: B (Solid) - 54/100

External PR Merge Rate: 65%

Response Time: 4h

First Timer Success: 74%

Frequently Asked Questions

Is Karanjot786/TermUI welcoming to first-time open-source contributors?

Karanjot786/TermUI has a recorded first-timer success rate of 73.9%. Repositories ranked B 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 Karanjot786/TermUI respond to incoming external pull requests in approximately 4.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 53.6 C-Rank™ score (B 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 53.6 places Karanjot786/TermUI in the B tier.

What is the external contributor pull request merge rate for Karanjot786/TermUI?

The external contributor pull request merge rate for Karanjot786/TermUI is 65.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Karanjot786/TermUI?

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

Karanjot786
Karanjot786/TermUIB•Solid236
GitHub
Back to Explorer
Karanjot786

Karanjot786/TermUI

236
Active (30d)B•Solid(54/100)TypeScript

TermUI is a TypeScript/JavaScript framework for building terminal apps. Flexbox layout, JSX, hooks, global state, theming, animations, routing, and hot reload. No native dependencies.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.6/10
Patience Score
8.2/10
Nitpick Rate
25%

Collaborative maintainer environment in Karanjot786/TermUI. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in Karanjot786/TermUI focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Keep PRs small and focused on one change
  • •Call out API, migration, or compatibility impact clearly

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not mix unrelated refactors with feature work
  • •Do not hide breaking changes in implementation details
Response Velocity
4 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
65.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
73.9%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
65.2%
Merge Gauge
73.9%
1st-Timer
Community Vibe75/100

Embed C-Rank Badge

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

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

Active Good First Issues (3)

View on GitHub

Summary The TermUI repository's README does not contain a comprehensive API reference or usage examples that would allow a new developer to integrate the library into their project. For a library project, documentation is as critical as the code itself — without it, adoption is impossible regardless of the library's technical quality. Problem The README does not document individual components, their props, or their expected behavior. There are no runnable code examples demonstrating how to use TermUI in a real terminal application. New contributors and potential library consumers cannot understand the library's capabilities without reading source code directly. There is no "Getting Started" section with installation instructions, a minimal working example, and an explanation of the component model. Impact Zero discoverability for developers searching for a terminal UI library — without documentation, TermUI cannot compete with alternatives like ink or blessed. GSSoC contributors

📅 Opened Aug 4, 2026💬 6 comments
Quality: 50/100Contribute

What to build Add a TokenUsage widget to packages/widgets/src/display/TokenUsage.ts. TokenUsage renders a context window meter showing used and total tokens with a colored progress bar. Acceptance criteria Accepts used: number, total: number. Renders: [########----] 1024 / 8192 tokens (12.5%) Color changes based on fill ratio: green below 80%, yellow from 80-95%, red above 95%. setUsed(n) updates the display. Calls this.markDirty(). Has a .test.ts with at least 4 tests: renders correct percentage, green below 80%, yellow at 85%, red at 96%. Implementation notes Place at packages/widgets/src/display/TokenUsage.ts. Export from packages/widgets/src/index.ts. Reuse ProgressBar internally for the bar render. Apply color via the bar's fillColor prop based on the ratio. Example usage const usage = new TokenUsage({ total: 8192, width: 40 }) usage.setUsed(1024) GSSoC 2026 This is an intermediate-level issue. Comment "I would like to work on this" to get assigned. You have 7 days to open a P

📅 Opened May 29, 2026💬 19 comments
Quality: 70/100Contribute

What to build Add a FormField widget to packages/ui/src/FormField.ts. FormField wraps any input widget with a label above and an optional error message below. Acceptance criteria Accepts label: string, error?: string, and a child widget. Renders the label above the child widget. When error is set, renders the error string below the child widget in red. When error is not set, no extra line renders below. Calls this.markDirty() when label or error changes. Has a .test.ts with at least 3 tests: label renders above, error renders below in red, no error = no extra line. Implementation notes Place at packages/ui/src/FormField.ts. Export from packages/ui/src/index.ts. Look at packages/ui/src/Form.ts for field wrapping patterns. Example usage const field = new FormField({ label: 'Username', error: 'Required' }) field.addChild(new TextInput({ placeholder: 'Enter username' })) GSSoC 2026 This is a beginner-level issue. Comment "I would like to work on this" to get assigned. You have 7 days t

📅 Opened May 29, 2026💬 9 comments
Quality: 70/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 Karanjot786/TermUI

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

Frequently Asked Questions - Contributing to Karanjot786/TermUI

01

Is Karanjot786/TermUI welcoming to first-time open-source contributors?

Karanjot786/TermUI has a recorded first-timer success rate of 73.9%. Repositories ranked Solid 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 ~4 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 53.6 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 53.6 places Karanjot786/TermUI in the Solid tier.

04

What is the external contributor pull request merge rate for Karanjot786/TermUI?

The external pull request merge rate is 65.2%. 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 Karanjot786/TermUI?

Yes, Karanjot786/TermUI currently has 3 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 Karanjot786/TermUI 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.