PEP-484 stubs for Django
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 85%
Response Time: 5h
First Timer Success: 70%
typeddjango/django-stubs has a recorded first-timer success rate of 70.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in typeddjango/django-stubs respond to incoming external pull requests in approximately 5.2 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 71.3 places typeddjango/django-stubs in the S tier.
The external contributor pull request merge rate for typeddjango/django-stubs is 85.2%, based on public PR activity from non-core contributors.
typeddjango/django-stubs currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in typeddjango/django-stubs. Prompt code reviews with positive guidance for new contributors.
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/typeddjango/django-stubs?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 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~25 hours (38% approval). Keep your diff compact for rapid review.
Description: Running ./scripts/stubtest.sh on the current version of django-stubs reveals several inconsistencies between the stubs and the runtime environment. Choices Classes Inconsistency (__init__ vs __new__) Multiple errors indicate that IntegerChoices and TextChoices define __init__ with parameters in the stubs, but at runtime, these parameters do not exist in __init__. The error message suggests moving the logic to __new__. Affected modules: django.db.models.enums django.contrib.gis.db.models django.tasks.base Example Error: error: django.db.models.enums.IntegerChoices.__init__ is inconsistent, runtime does not have parameter "x". You may need to write stubs for __new__ instead of __init__. Stub: Overload(def (self: ..., x: ...), def (self: ..., x: ..., label: ...)) Runtime: def (self) Missing members in django.utils.inspect The runtime has lock and safe_signature_from_callable which are completely missing from the stubs. Errors: error: django.utils.inspect.lock is
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 typeddjango/django-stubs, 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 typeddjango/django-stubs acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.2% were successfully merged into the primary branch.
typeddjango/django-stubs has a recorded first-timer success rate of 70.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 71.3 places typeddjango/django-stubs in the Elite tier.
The external pull request merge rate is 85.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, typeddjango/django-stubs 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 typeddjango/django-stubs 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.