A local desktop app that turns videos and images into 3D Gaussian Splats in one click.
C-Rank Grade: D (Risky) - 13/100
External PR Merge Rate: -
Response Time: 9d
First Timer Success: -
ooolabdev/ooosplat has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ooolabdev/ooosplat respond to incoming external pull requests in approximately 213.4 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 13.4 places ooolabdev/ooosplat in the D tier.
The external contributor pull request merge rate for ooolabdev/ooosplat is 0.0%, based on public PR activity from non-core contributors.
ooolabdev/ooosplat does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in ooolabdev/ooosplat. Reviews community pull requests with focus on project quality.
Discussions in ooolabdev/ooosplat 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/ooolabdev/ooosplat?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~139 hours (81% approval). Large PRs (>500 lines) take ~1025 hours (29% approval). Keep your diff compact for rapid review.
## 概述 对 `0.2.0` 做了一轮静态走查，发现 5 处值得修复的缺陷，按影响排序。全部可在本地复现或由代码逻辑直接推出。 --- ### 1. PLY 头解析脆弱，可能在训练完成后误判产物无效（最高优先级） `src-tauri/src/reconstruction/ply.rs:18-21` ```rust let mut bytes = vec![0_u8; (size.min(256 * 1024)) as usize]; let read = file.read(&mut bytes)?; Read::read 允许短读，返回少于 256KB 也合法。此时 end_header 可能落在未读区域，报错「PLY 缺少 end_header」。失败点在 Brush 训练完成之后，用户损失最大。 ply.rs:37-49 属性校验用 line.ends_with(" x")，但 header.lines() 会保留 CRLF 的 \r，CRLF 头必然匹配失败，报「PLY 缺少 Gaussian 属性」。而同函数 :26 又显式接受 ply\r\n，逻辑自相矛盾。 建议：改用 file.take(n).read_to_end(&mut bytes)；所有头行统一 trim_end() 后再比较。 2. 失败/取消时进度条跳到 100%，时间线全部
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 ooolabdev/ooosplat, 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 ooolabdev/ooosplat acknowledge new external contributions in approximately 8 days+. 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.
ooolabdev/ooosplat has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 days+. 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 13.4 places ooolabdev/ooosplat in the Risky 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.
ooolabdev/ooosplat does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for ooolabdev/ooosplat 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.