Just another ComputerCraft fork
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 67%
Response Time: 4h
First Timer Success: -
cc-tweaked/CC-Tweaked 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 cc-tweaked/CC-Tweaked 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.
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 47.1 places cc-tweaked/CC-Tweaked in the B tier.
The external contributor pull request merge rate for cc-tweaked/CC-Tweaked is 66.7%, based on public PR activity from non-core contributors.
cc-tweaked/CC-Tweaked currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in cc-tweaked/CC-Tweaked. Reviews pull requests with focus on project architectural goals.
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/cc-tweaked/CC-Tweaked?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Java.
Knowage is the professional open source suite for modern business analytics over traditional sources and big data systems.
DITA Open Toolkit — the open-source publishing engine for content authored in the Darwin Information Typing Architecture.
Agents-flex is A lightweight Java AI agent development framework (positioned as a counterpart to Spring AI). It supports features such as RAG, MCP, Skills, Text2SQL , LLM Wiki, Sub-agents, Web Search, TTS (synchronous and streaming), and STT.
Minecraft Version 1.20.1 Version 1.119.0 Details Using turtle.place on a water bucket in any direction (up, down, or forward) with an air block then a waterlog-able block will water log the block rather than the air gap between them: A couple of other observations when it comes to water placement: When there is an air block then a solid block (a block that can't be waterlogged) in a direction, turtle.place in that direction will place it in the air block When there are 2 air blocks in a direction, turtle.place will waterlog the turtle (maybe the logic here is causing the bugged behavior with the air block? don't know enough about modding myself to check) You can water log and drain the turtle with a solid block directly next to the turtle in every direction, minus draining the water with turtle.placeUp. Waterlogging with turtle.placeUp seems to work fine, draining with placeUp and a block above results in "Cannot place item here" Lava always places as expected
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 cc-tweaked/CC-Tweaked, 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 cc-tweaked/CC-Tweaked acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
cc-tweaked/CC-Tweaked 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 ~4 hours. 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 47.1 places cc-tweaked/CC-Tweaked in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cc-tweaked/CC-Tweaked currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for cc-tweaked/CC-Tweaked 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.