google/xrblocks - Open Source PR Review Scorecard

XR Blocks is a lightweight WebXR + AI library for rapidly prototyping advanced AI + XR experiences.

C-Rank Grade: S (Elite) - 81/100

External PR Merge Rate: 93%

Response Time: 4h

First Timer Success: 85%

Frequently Asked Questions

Is google/xrblocks welcoming to first-time open-source contributors?

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

What does the 81.3 C-Rank™ score (S 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 81.3 places google/xrblocks in the S tier.

What is the external contributor pull request merge rate for google/xrblocks?

The external contributor pull request merge rate for google/xrblocks is 92.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in google/xrblocks?

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

google
google/xrblocksSElite465
GitHub
Back to Explorer
google

google/xrblocks

465
SElite(81/100)TypeScript

XR Blocks is a lightweight WebXR + AI library for rapidly prototyping advanced AI + XR experiences.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
9.5/10
Patience Score
9.6/10
Nitpick Rate
20%

Highly welcoming maintainers in google/xrblocks. 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
3 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
92.5%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
13 core
Highly collaborative maintainer core
Diagnostic Health HUD
92.5%
Merge Gauge
84.6%
1st-Timer
Community Vibe90/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Hi there! Thank you for contributing to XR Blocks! In additional to CONTRIBUTING.md, I'd like to highlight a few contributing point: Demo contributors: for first-time contributor, a new demo that demonstrates novel features in interactive perception, XR realism, embodied interactions, interactive graphics, Gemini capabilities are preferred. E.g., 1) novel use case with open Hugging Face models, 2) port more https://github.com/googlesamples/arcore-depth-lab and https://github.com/google/archat features to XR, 3) converting MIT / Apache 2 shader to XR: https://www.shadertoy.com/view/4sX3Rn (also remember to give credits in README. 4) Finding novel use case of Gemini :) 5) adding accessibility and security layers. All demo submissions should attach an unlisted YouTube video, or screenshots for the expected output. SDK contributors: For small changes, just submit PR; for large changes, maybe create an issue to discuss high-level design first :) Also read https://arxiv.org/abs/2509.25504 a

📅 Opened May 14, 2026💬 0 comments
Quality: 80/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 google/xrblocks

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

Frequently Asked Questions - Contributing to google/xrblocks

01

Is google/xrblocks welcoming to first-time open-source contributors?

google/xrblocks has a recorded first-timer success rate of 84.6%. Repositories ranked Elite 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 ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 81.3 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 81.3 places google/xrblocks in the Elite tier.

04

What is the external contributor pull request merge rate for google/xrblocks?

The external pull request merge rate is 92.5%. 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 google/xrblocks?

Yes, google/xrblocks currently has 1 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 google/xrblocks 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.