Open-source app for turning images into stacked, color-layered 3D prints. Optimize filament order with physics-based auto-painting, preview every layer in 2D and 3D, calibrate filament hiding distance, and export print-ready STL or 3MF files.
C-Rank Grade: D (Risky) - 16/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
vycdev/Kromacut 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 vycdev/Kromacut 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 15.7 places vycdev/Kromacut in the D tier.
The external contributor pull request merge rate for vycdev/Kromacut is 0.0%, based on public PR activity from non-core contributors.
vycdev/Kromacut currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source app for turning images into stacked, color-layered 3D prints. Optimize filament order with physics-based auto-painting, preview every layer in 2D and 3D, calibrate filament hiding distance, and export print-ready STL or 3MF files.
Active maintainer team in vycdev/Kromacut welcoming community pull requests and bug fixes.
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/vycdev/Kromacut?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19: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.
Request Add links to the Kromacut tutorial and the original introduction video in README.md, so visitors can easily find both. Videos Tutorial: Turn Any Image into a Multicolor 3D Print | Kromacut Tutorial First video / introduction: I Recreated the Industry’s Most Advanced 3D Printing App… For Free Acceptance criteria Both videos are linked from a clearly labeled section of the README. The tutorial and introductory video are clearly distinguished. The links render correctly on GitHub and existing documentation links remain available.
Summary Remove the ## Star History section and its linked chart from README.md. Why GitHub changed the API access used by the embedded Star History chart, and the graph no longer works without supplying a GitHub token. Kromacut should not need or maintain a token just to render a README graph, so the broken integration should be removed. Scope Remove the ## Star History heading. Remove the linked star-history.com chart directly below it. Keep the surrounding release documentation and ## Contributing section intact. Avoid unrelated README changes. Acceptance criteria README.md no longer contains the Star History section. No star-history.com URL remains in the README. The README still renders cleanly, with normal spacing before ## Contributing. No application code or behavior is changed. This should be a straightforward first contribution; no build or test run is expected for this documentation-only change.
Goal Create a polished 1280 x 640 Social Preview banner for Kromacut. This is the image configured under Repository settings > Social preview and shown when the repository link is shared. Design direction Communicate Kromacut's core idea: turning a 2D image into a stacked, color-layered 3D print. Reuse the Kromacut logo and existing visual language where appropriate. Keep the design clear and recognizable at small preview sizes. Keep important content inside the safe area shown by the template below so it is not cropped. Deliverables A final 1280 x 640 PNG or JPG suitable for GitHub's Social Preview setting. The editable source file, if possible. Template Use this template as the size and safe-area reference: Submissions Please post proposed Social Preview images directly in this issue. I'll review the submissions and close the issue once I find a suitable banner for the repository.
Kromacut would benefit from a validation pass comparing its color and TD behavior against equivalent HueForge workflows. This is not necessarily a request to copy HueForge behavior. The goal is to better understand where Kromacut matches expectations, where it differs, and whether those differences point to bugs, calibration issues, UX gaps, or intentional model differences. This likely needs help from someone who has access to HueForge. Useful comparison areas: Same source image processed in Kromacut and HueForge. Same or comparable filament colors and TD values. Similar layer height, total height, and print settings. Previewed output comparison. Printed output comparison, if possible. Notes on where Kromacut appears more/less accurate. Cases where TD values produce unexpected results. Cases where auto-paint choices differ significantly. Possible outputs from this research: Example images and project/settings files. Screenshots of both previews. Photos of printed results. Notes on
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 vycdev/Kromacut, 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 vycdev/Kromacut 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.
vycdev/Kromacut 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 ~-. 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 15.7 places vycdev/Kromacut 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.
Yes, vycdev/Kromacut currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for vycdev/Kromacut 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.