AI-powered Docker security scanner that explains vulnerabilities in plain English. An OWASP Lab Project.
C-Rank Grade: B (Solid) - 56/100
External PR Merge Rate: 56%
Response Time: 12h
First Timer Success: 100%
OWASP/DockSec has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in OWASP/DockSec respond to incoming external pull requests in approximately 11.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 55.7 places OWASP/DockSec in the B tier.
The external contributor pull request merge rate for OWASP/DockSec is 55.6%, based on public PR activity from non-core contributors.
OWASP/DockSec currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in OWASP/DockSec. Reviews community pull requests with focus on project quality.
Discussions in OWASP/DockSec 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/OWASP/DockSec?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (69% approval). Large PRs (>500 lines) take ~56 hours (25% approval). Keep your diff compact for rapid review.
Background Found while manually testing --compose against examples/compose/docker-compose-insecure.yml with images not pulled locally. When a per-service image scan fails inside ComposeOrchestrator.run_full_scan (docksec/compose_scanner.py, around lines 387-432), the failure is only logged via logger.error(...), which is invisible by default in CLI mode (logger defaults to ERROR-and-up on stderr, but even then a user running without -v/DOCKSEC_LOG_LEVEL won't see it prominently — see #129 for adding -v). The scan otherwise completes and reports a security score as if every service's image had actually been scanned, which can be misleading: a user could believe the compose scan was comprehensive when some services silently only got static rule checks, not real vulnerability data. Task When one or more services fail to scan (image not found locally, scanner exception, etc.), surface this clearly in the CLI's user-facing output — not just the debug log. For example, add a line to the
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 OWASP/DockSec, 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 OWASP/DockSec acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.6% were successfully merged into the primary branch.
OWASP/DockSec has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 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 OWASP/DockSec in the Solid tier.
The external pull request merge rate is 55.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, OWASP/DockSec 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 OWASP/DockSec 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.