A community-maintained Python framework for creating mathematical animations.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 31%
Response Time: 21h
First Timer Success: 42%
ManimCommunity/manim has a recorded first-timer success rate of 41.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ManimCommunity/manim respond to incoming external pull requests in approximately 21.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 55.7 places ManimCommunity/manim in the A tier.
The external contributor pull request merge rate for ManimCommunity/manim is 30.7%, based on public PR activity from non-core contributors.
ManimCommunity/manim currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in ManimCommunity/manim. Maintains strict focus on technical quality and test standards.
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/ManimCommunity/manim?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (38% approval). Large PRs (>500 lines) take ~102 hours (15% approval). Keep your diff compact for rapid review.
Description of proposed feature Currently, the config is often accessed via config["some_attribute"] I think it would be better to replace all of these with config.some_attribute as that preserves the attribute type and prevents typos. It is probably a good idea to spread this over multiple PRs.
The class CurvesAsSubmobjects throws two custom error messages for when it either has no submobjects or it has no submobjects with points: manim/manim/mobject/types/vectorized_mobject.py Lines 2858 to 2874 in cafc639 def _throw_error_if_no_submobjects(self): if len(self.submobjects) == 0: caller_name = sys._getframe(1).f_code.co_name raise Exception( f"Cannot call CurvesAsSubmobjects. {caller_name} for a CurvesAsSubmobject with no submobjects" ) def _get_submobjects_with_points(self): submobjs_with_pts = tuple(
Description of proposed feature Warnings messages to the user should include the stack trace, so the user knows where it was caused from. logger.warning( "Don't do ...", stack_info=True, stacklevel=2, )
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 ManimCommunity/manim, 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 ManimCommunity/manim acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 30.7% were successfully merged into the primary branch.
ManimCommunity/manim has a recorded first-timer success rate of 41.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 55.7 places ManimCommunity/manim in the Welcoming tier.
The external pull request merge rate is 30.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ManimCommunity/manim 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 ManimCommunity/manim 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.