Open Reality: phone video to AI-queryable 3D scenes. MCP tools for Claude/Codex/Cursor (npm openreality-mcp), the self-hostable broker, and the VGGT-SLAM library, in one repo. BSD-2-Clause.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
reality-opened/openreality 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.
Maintainers in reality-opened/openreality respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 45.6 places reality-opened/openreality in the B tier.
The external contributor pull request merge rate for reality-opened/openreality is 0.0%, based on public PR activity from non-core contributors.
reality-opened/openreality currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in reality-opened/openreality. Reviews community pull requests with focus on project quality.
Discussions in reality-opened/openreality focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/reality-opened/openreality?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
The CLI is developed on macOS and Linux. On Windows we have not verified: the browser hand-off in openreality-mcp login, the credentials file location (currently ~/.config/openreality/credentials.json; should probably follow %APPDATA% on Windows), and artifact download paths. If you run Windows, please try the Quickstart in mcp/README.md with the simulator (no account needed) and report what breaks, or send a PR. The Claude desktop extension (.mcpb) declares win32 support and needs the same check.
server/docs/self-hosting.md documents Path A (python -m server.selfhost on your own GPU machine) as a bare Python process. A docker-compose.yml with a CUDA base image, the pinned VGGT_SPARK checkout, a mounted --data-dir volume, and the first-start token printed to the logs would make self-hosting a one-command affair. Licensing constraint: the compose file must fetch the backbone model at first run, never bake it into an image (see the licensing note in the root README). Please include a short 'how I tested it' note (GPU, driver, time to first reconstruction) in the PR.
The offline simulator (openreality-mcp simulator) ships scenes that measure in relative units until scene_anchor is called, which is the honest default. For demos and tests of the metric-gated paths (Isaac export, units:"m" responses) it would help to have one fixture scene that starts anchored, with scale_source set to describe the anchor. Add it to mcp/simulator/, make sure scene_card reports the metric state correctly, and add a contract test in test/simulator.contract.test.ts. Do not change the default un-anchored fixtures.
openreality-mcp whoami and openreality-mcp keys list print human-readable text. Scripts and agents that wrap the CLI would like machine-readable output. Add --json to both subcommands (print the same data as a single JSON object / array on stdout, nothing else) and cover it in test/login.test.ts. Entry point: mcp/src/cli.ts. Keep the default output unchanged.
README.md and README.zh.md are kept as translations of each other, but the measurement-honesty post at docs/posts/relative-units-are-not-metres.md exists only in English. Add docs/posts/relative-units-are-not-metres.zh.md and link it from README.zh.md (replace the '（英文）' note next to the existing link). House rules: no em dashes, plain language, define jargon on first use (SLAM, MCP, splat).
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to reality-opened/openreality, 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 reality-opened/openreality acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
reality-opened/openreality 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.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 45.6 places reality-opened/openreality in the Solid tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, reality-opened/openreality currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for reality-opened/openreality 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.