⭐ Concat: The truly free, and open-source cross-platform CapCut replacement (supports MCPs).
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 31%
Response Time: <1h
First Timer Success: 60%
jub0t/Concat has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jub0t/Concat respond to incoming external pull requests in approximately 0.7 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 63.2 places jub0t/Concat in the A tier.
The external contributor pull request merge rate for jub0t/Concat is 31.0%, based on public PR activity from non-core contributors.
jub0t/Concat currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in jub0t/Concat. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in jub0t/Concat 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/jub0t/Concat?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (39% approval). Large PRs (>500 lines) take ~3 hours (15% approval). Keep your diff compact for rapid review.
We need to test this thing:
Right now videos on the timeline only show the visual frames at different timestamps but they do not show the audio related to the video. TODO: Add a section under the video preview that shows that video's audio waveform, if the video has no audio, still show the section but with zero/empty waveform pattern.
Create a docs/ directory in the repository where all the documentation for MCPs, JSON API, and gRPC exists and receives updates.
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 jub0t/Concat, 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 jub0t/Concat acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 31.0% were successfully merged into the primary branch.
jub0t/Concat has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 63.2 places jub0t/Concat in the Welcoming tier.
The external pull request merge rate is 31.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jub0t/Concat currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jub0t/Concat 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.