cboard-org/cboard - Open Source PR Review Scorecard

Augmentative and Alternative Communication (AAC) system with text-to-speech for the browser

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

External PR Merge Rate: 82%

Response Time: 11h

First Timer Success: 100%

Frequently Asked Questions

Is cboard-org/cboard welcoming to first-time open-source contributors?

cboard-org/cboard 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.

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

Maintainers in cboard-org/cboard respond to incoming external pull requests in approximately 11.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 63.2 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 63.2 places cboard-org/cboard in the A tier.

What is the external contributor pull request merge rate for cboard-org/cboard?

The external contributor pull request merge rate for cboard-org/cboard is 82.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in cboard-org/cboard?

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

cboard-org
cboard-org/cboardA•Welcoming757
GitHub
Back to Explorer
cboard-org

cboard-org/cboard

757
InactiveA•Welcoming(63/100)Low Sample (<20 PRs)JavaScript

Augmentative and Alternative Communication (AAC) system with text-to-speech for the browser

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in cboard-org/cboard welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
11 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
82.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
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
82.4%
Merge Gauge
100.0%
1st-Timer
Community Vibe84/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Summary Recorded tile sounds are uploaded with a hardcoded .mp3 filename, but the actual recording format depends on the browser. We should derive the correct file extension from the audio's real MIME type instead of assuming .mp3. Background VoiceRecorder uses MediaRecorder with no explicit mimeType, so the output format is browser-dependent: Chrome → audio/webm Firefox → audio/ogg Safari → audio/mp4 The base64 sound is later uploaded to /media. Both upload paths name the file .mp3 regardless of the real format: src/api/api.js — uploadTileSoundMedia calls uploadFromDataURL(tile.sound, ${tile.id}.mp3) src/components/Board/Board.container.js — uploadTileSound uploads userData.email + '.mp3' and also hardcodes the Blob type to audio/mp3; codecs=opus Is this currently breaking anything? No — this is a cleanup / correctness-polish task, not a live bug. The media server appears to infer content-type from the upload's MIME type, not the filename extension (evidence: tile imag

📅 Opened Jun 29, 2026💬 1 comment
Quality: 90/100Contribute

Summary Convert Export from a class component to a functional component. This aligns with the rest of the codebase's direction and removes unnecessary boilerplate. What changes State — replace 7 this.state fields with individual useState calls: exportSingleBoard, exportAllBoard, singleBoard, labelFontSize, loadingSingle, loadingAll, boardError Methods — convert class methods to regular functions / useCallback: handleBoardChange, handleSizeChange, handleSingleBoardChange, handleAllBoardChange, handleSingleExport, handleAllExport Dead code removal — openMenu and closeMenu are defined but never called and exportMenu is never read in render. Remove them. Custom hook Extract a useExportLoading hook at the top of Export.component.js (not a separate file — it's only used here). Both handleSingleExport and handleAllExport share the same pattern: set a loading flag → call onExportClick with a done-callback → clear the flag. Extracting it avoids duplicating that logic: function u

📅 Opened Apr 13, 2026💬 2 comments
Quality: 70/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript 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 cboard-org/cboard

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

Frequently Asked Questions - Contributing to cboard-org/cboard

01

Is cboard-org/cboard welcoming to first-time open-source contributors?

cboard-org/cboard 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.

02

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

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

03

What does the 63.2 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 63.2 places cboard-org/cboard in the Welcoming tier.

04

What is the external contributor pull request merge rate for cboard-org/cboard?

The external pull request merge rate is 82.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 cboard-org/cboard?

Yes, cboard-org/cboard currently has 2 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 cboard-org/cboard 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.