SolidCraft: an open-source parametric 3D CAD application built in pure Rust. Desktop, web, and automation through MCP.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 15%
Response Time: -
First Timer Success: -
bherbruck/solidcraft has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bherbruck/solidcraft 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 60.3 places bherbruck/solidcraft in the A tier.
The external contributor pull request merge rate for bherbruck/solidcraft is 14.6%, based on public PR activity from non-core contributors.
bherbruck/solidcraft currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in bherbruck/solidcraft. Prompt code reviews with positive guidance for new contributors.
Discussions in bherbruck/solidcraft 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/bherbruck/solidcraft?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (18% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
An open-ended performance umbrella for anyone who wants to dig in. @0xlillith, this looks like your kind of thing if you're interested, but anyone is welcome to pick off a piece. Please open a separate PR per item, and measure first: include before/after timings (and add them to docs/perf.md). Today almost everything runs on one thread. Nothing in crates/kernel, crates/doc or the readers uses threads; the only exception is a background file task in crates/io/src/vfs.rs. There is already an in-memory evaluation cache (EvalCache in crates/doc/src/eval.rs) and recent cold-rebuild work (400f200, docs/perf.md). Ideas, roughly in order of likely payoff 1. Parallel STEP/IGES import Build independent solids and assembly parts concurrently after parsing (crates/kernel/src/step_in). Big assemblies should benefit most. The text parse itself is probably not worth splitting. 2. Parallel tessellation and mass properties One body, or one face, per task, for display meshes, measure, snapshots and expo
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!
Filleting three edges that meet at a box corner, with three different radii, gives one smooth 3-sided corner patch. It is tangent to the three cylinders within 0.01°, closed, and has 10 faces. A 6-sided setback patch is the common alternative: each round stops short of the corner, and the patch also meets the three planar faces. It gives a smoother, more even transition for unequal radii. Open questions: the setback distance rule for each round (a candidate: the two larger rounds stop at S/3 plus the other larger radius from the corner, where S is the sum of the radii; the smallest round's rule is unclear); a single smooth face over the 6-gon versus three quads (three quads give 12 faces). This is optional, as an alternative corner type alongside the current one.
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.
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.
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 bherbruck/solidcraft, 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/solidcraft acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 14.6% were successfully merged into the primary branch.
bherbruck/solidcraft has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming 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 60.3 places bherbruck/solidcraft in the Welcoming tier.
The external pull request merge rate is 14.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bherbruck/solidcraft 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 bherbruck/solidcraft 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.