Open-Source Unified Vulnerability Management, DevSecOps & ASPM
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 83%
Response Time: -
First Timer Success: 100%
DefectDojo/django-DefectDojo has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DefectDojo/django-DefectDojo respond to incoming external pull requests in approximately 0.0 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 70.5 places DefectDojo/django-DefectDojo in the S tier.
The external contributor pull request merge rate for DefectDojo/django-DefectDojo is 83.0%, based on public PR activity from non-core contributors.
DefectDojo/django-DefectDojo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in DefectDojo/django-DefectDojo welcoming community pull requests and bug fixes.
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/DefectDojo/django-DefectDojo?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Bug description When using the bulk select button to select a given set of findings, proceeding to select the merge button does not respect the amount of findings that have been selected. Always stating that "you need to select at least 2 findings" requiring I deselect and reselect individual findings first on top of the bulk select to merge a large amount of findings. To clarify when actually performing the merge all the findings selected in view are merged, the bug is with the fact you have to unnecessarily reselect findings for the merge button to let you merge. Steps to reproduce the behavior: Go to any list of findings. Use the bulk select to select a subset or all findings. Attempt to use the merge button to merge findings. Intended behavior: When using the bulk selector the merge button should be aware of the quantity selected to allow for merging without needing to explicitly reselect 2 findings. Deployment method (select with an X): [X ] Docker Compose Environment information:
The current regulation.json fixture is missing several important modern regulations: ISO/IEC 42001:2023 (AI Management Systems) EU AI Act (2024) NIS2 Directive (EU) 2022/2555 DORA (Digital Operational Resilience Act) ISO/IEC 27701:2019 (Privacy Information Management) I would like to add these to the fixture file. Happy to submit a PR if this is approved.
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 DefectDojo/django-DefectDojo, 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 DefectDojo/django-DefectDojo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.0% were successfully merged into the primary branch.
DefectDojo/django-DefectDojo has a recorded first-timer success rate of 100.0%. Repositories ranked Elite 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 70.5 places DefectDojo/django-DefectDojo in the Elite tier.
The external pull request merge rate is 83.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, DefectDojo/django-DefectDojo currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for DefectDojo/django-DefectDojo 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.