bherbruck/solvecraft - Open Source PR Review Scorecard

An open-source, clean-room reimplementation of Autodesk Fusion 360 in pure Rust. Parametric 3D CAD for desktop, browser, and AI agents via MCP.

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

External PR Merge Rate: 20%

Response Time: 4h

First Timer Success: -

Frequently Asked Questions

Is bherbruck/solvecraft welcoming to first-time open-source contributors?

bherbruck/solvecraft 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 bherbruck/solvecraft respond to incoming external pull requests in approximately 4.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 50.9 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 50.9 places bherbruck/solvecraft in the B tier.

What is the external contributor pull request merge rate for bherbruck/solvecraft?

The external contributor pull request merge rate for bherbruck/solvecraft is 20.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in bherbruck/solvecraft?

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

bherbruck
bherbruck/solvecraftB•Solid157
GitHub
Back to Explorer
bherbruck

bherbruck/solvecraft

157
Active (30d)B•Solid(51/100)Low Sample (<20 PRs)Rust

An open-source, clean-room reimplementation of Autodesk Fusion 360 in pure Rust. Parametric 3D CAD for desktop, browser, and AI agents via MCP.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.9/10
Patience Score
8.4/10
Nitpick Rate
20%

Highly welcoming maintainers in bherbruck/solvecraft. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in bherbruck/solvecraft 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
4 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
20.0%
Selective PR acceptance rate

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
2 core
Small core review team
Diagnostic Health HUD
20.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe35/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

Unlike the apps from ArtCraft, this app is not recognized. I had to 'enable' it in security / "open anyways", then it worked. I'm trilled to experiment more, and see more. The MCP part is very interesting!

📅 Opened Oct 11, 2026💬 0 comments
Quality: 60/100Contribute

Fillets on three edges at a box corner with three different radii come out as one smooth 3-sided corner patch (tangent to the three cylinders within 0.01°, closed, 10 faces like Fusion). Fusion builds a 6-sided setback patch there instead. Our volume differs from Fusion's by: radii (A,B,C) Fusion mm³ ours mm³ delta (2,3,3) 7900.664 7908.921 +0.105% (2,3,4) 7867.820 7880.464 +0.161% (1,2,3) 7937.490 7941.503 +0.051% (3,3,1) 7914.849 7921.270 +0.081% (2,3,6) 7794.490 7798.774 +0.055% Equal radii (a sphere) and (r, r, R) (a torus) match within 0.006%. The data is in solvecraft-tools/corner_cases/ (local, Fusion-produced, never commit): setback_cases.json and case3_patch.json (patch vertices, loop edges, NURBS data). It covers a 20 mm box with A = edge x=20,z=20, B = y=0,z=20, C = x=20,y=0 at the corner (20,0,20). Fitted rule (fits all four 6-sided cases). S = ra + rb + rc. The two larger rounds end S/3 + (the other larger radius) from the corner. On the face between

📅 Opened Oct 9, 2026💬 1 comment
Quality: 90/100Contribute

About half of randomly generated designs evaluate without a kernel error. Every failing seed is a reproducible bug; the fuzzer reports the failing feature and seed.

📅 Opened Oct 9, 2026💬 2 comments
Quality: 75/100Contribute

Constant, chord and two-ended variable-radius fillets work, and so do corners where rounds of different radii meet (crease) and three rounds at a vertex (corner patch). Missing: Fusion's Setback corner type, and variable radius with radii at points along the edge.

📅 Opened Oct 9, 2026💬 1 comment
Quality: 75/100Contribute
Looking for more Rust beginner tasks?Explore Rust 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 bherbruck/solvecraft

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

Frequently Asked Questions - Contributing to bherbruck/solvecraft

01

Is bherbruck/solvecraft welcoming to first-time open-source contributors?

bherbruck/solvecraft 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 ~4 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 50.9 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 50.9 places bherbruck/solvecraft in the Solid tier.

04

What is the external contributor pull request merge rate for bherbruck/solvecraft?

The external pull request merge rate is 20.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 bherbruck/solvecraft?

Yes, bherbruck/solvecraft 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 bherbruck/solvecraft 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.