tanpreetjolly/browser-whisper - Open Source PR Review Scorecard

In-browser Whisper speech-to-text with WebGPU (WASM fallback). Transcribe audio & video locally, no server.

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

External PR Merge Rate: 100%

Response Time: 6d

First Timer Success: -

Frequently Asked Questions

Is tanpreetjolly/browser-whisper welcoming to first-time open-source contributors?

tanpreetjolly/browser-whisper has a recorded first-timer success rate of 0.0%. 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 tanpreetjolly/browser-whisper respond to incoming external pull requests in approximately 141.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 43.2 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 43.2 places tanpreetjolly/browser-whisper in the B tier.

What is the external contributor pull request merge rate for tanpreetjolly/browser-whisper?

The external contributor pull request merge rate for tanpreetjolly/browser-whisper is 100.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in tanpreetjolly/browser-whisper?

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

tanpreetjolly
tanpreetjolly/browser-whisperB•Solid204
GitHub
Back to Explorer
tanpreetjolly

tanpreetjolly/browser-whisper

204
Active (30d)B•Solid(43/100)Low Sample (<20 PRs)TypeScript

In-browser Whisper speech-to-text with WebGPU (WASM fallback). Transcribe audio & video locally, no server.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

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

Collaborative maintainer environment in tanpreetjolly/browser-whisper. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in tanpreetjolly/browser-whisper 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

  • •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
5 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
100.0%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
100.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe40/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

Model sizes are hand-copied in four places and had drifted (fixed in #15): the table in docs/index.html (#models), the table in README.md, the model picker in demo/index.html, and the picker in examples/live-vad/index.html. examples/mp3/index.html has no sizes at all. Task: add scripts/model-sizes.ts (run with bun) that reads MODELS from src/types.ts and, for each model, sums the file sizes from https://huggingface.co/api/models/<hfId>/tree/main/onnx for the files actually loaded with hybrid quantization (encoder_model.onnx + decoder_model_merged_q4.onnx for Whisper; encoder_model_q4.onnx + decoder_model_merged_q4.onnx for Moonshine; include any *.onnx_data files), and prints a Markdown table. Optionally add the sizes to the examples/mp3 picker.

📅 Opened Oct 10, 2026💬 0 comments
Quality: 90/100Contribute

TranscribeStream.cancel() / TranscribePCMStream.cancel() and BrowserWhisper.dispose() exist in src/browser-whisper.ts (around lines 131, 304, 403) but are not mentioned in README.md or the API reference in docs/index.html (section #api). Task: add a short section with a usage snippet (e.g. cancelling a long transcription from a button, and calling dispose() when unmounting a component to terminate the workers) to both files.

📅 Opened Oct 10, 2026💬 0 comments
Quality: 90/100Contribute

src/types.ts defines the MODELS map (Hugging Face ids, hybridDtype, timestamp/language flags), but there is no test covering it (src/tests/ has chunker, errors, opfs-cache, resampler, webgpu, word-segments). Task: add src/tests/models.test.ts (bun test) asserting, for example: every ASRModel key has an onnx-community/... hfId every *_timestamped model has supportsWordTimestamps: true English-only models (moonshine-*, distil-whisper-small) have supportsLanguage: false Moonshine models have supportsTimestamps: false Run with bun test.

📅 Opened Oct 10, 2026💬 0 comments
Quality: 90/100Contribute

The only workflow today is .github/workflows/publish.yml, which runs typecheck/test/build only when a release is published. PRs get no automated checks. Task: add .github/workflows/ci.yml triggered on pull_request and push to main that: uses oven-sh/setup-bun@v2 runs bun install --frozen-lockfile, bun run typecheck, bun test, bun run build, bun run build:site You can copy the setup steps from publish.yml. See CONTRIBUTING.md for the commands.

📅 Opened Oct 10, 2026💬 0 comments
Quality: 90/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 tanpreetjolly/browser-whisper

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

Frequently Asked Questions - Contributing to tanpreetjolly/browser-whisper

01

Is tanpreetjolly/browser-whisper welcoming to first-time open-source contributors?

tanpreetjolly/browser-whisper has a recorded first-timer success rate of 0.0%. 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 ~5 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 43.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 43.2 places tanpreetjolly/browser-whisper in the Solid tier.

04

What is the external contributor pull request merge rate for tanpreetjolly/browser-whisper?

The external pull request merge rate is 100.0%. 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 tanpreetjolly/browser-whisper?

Yes, tanpreetjolly/browser-whisper 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 tanpreetjolly/browser-whisper 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.