Local-first visual generation runtime and studio for people and coding agents, with reproducible image and video workflows across multiple providers.
C-Rank Grade: D (Risky) - 0/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
This repository currently has no indexed public pull request reviews or activity on GitHub. Some large projects conduct code reviews via external tooling (e.g. Gerrit, Phabricator) or internal monorepos. As soon as public PR review activity is recorded, scores are computed automatically.
No public review history has been recorded on GitHub for this project yet. Check the project CONTRIBUTING guide or explore active, welcoming alternatives in the same language ecosystem.
No public pull request merge data is recorded on GitHub for lidge-jun/ima2-gen. Review workflows may be hosted externally or restricted to core teams.
Review speed is currently unmeasured due to no public GitHub PR activity. Refer to the repository's contributing guidelines for team workflow norms.
lidge-jun/ima2-gen does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Local-first visual generation runtime and studio for people and coding agents, with reproducible image and video workflows across multiple providers.
We score this repo live from GitHub's public pull-request history - usually in under 30 seconds. Results are cached for 24 hours and refreshed when new commits land.
This repository has no indexed public pull request reviews or activity on GitHub yet. Some large projects conduct code reviews via external tooling or private repositories. As soon as public PR review activity is recorded, C-Rankâ„¢ computes scores automatically.
Strict review standards in lidge-jun/ima2-gen. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in lidge-jun/ima2-gen 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/lidge-jun/ima2-gen?utm_source=github&utm_medium=badge)
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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
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.
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 TypeScript.
DeepSeek Harness: Everything is a Plugin.
Curated coding interview preparation materials for busy software engineers
Collection of TypeScript type challenges with online judge
No cached good first issues currently tracked for lidge-jun/ima2-gen.
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 lidge-jun/ima2-gen, 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 lidge-jun/ima2-gen 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.
lidge-jun/ima2-gen 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 0.0 places lidge-jun/ima2-gen 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.
lidge-jun/ima2-gen 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 lidge-jun/ima2-gen 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.