This is a repo to house some common tools for our various docker repos.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 87%
Response Time: 20h
First Timer Success: 88%
dotnet/docker-tools has a recorded first-timer success rate of 87.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dotnet/docker-tools respond to incoming external pull requests in approximately 19.9 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 73.0 places dotnet/docker-tools in the S tier.
The external contributor pull request merge rate for dotnet/docker-tools is 87.4%, based on public PR activity from non-core contributors.
dotnet/docker-tools currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in dotnet/docker-tools. 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/dotnet/docker-tools?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (96% approval). Large PRs (>500 lines) take ~95 hours (39% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in C#.
A sleek, highly customizable timer for speedrunners.
Generate DTOs, mappings, constructors and LINQ projections from your domain models.
C compiler for the CLI platform
If signing is enabled, the Publish job should verify the signatures of images before copying them to the publish repo prefix. This would prevent accidental publishing of unsigned images or publishing invalid signatures.
Currently, the ImageBuilder notation trust policy does not include a TSA trust store: docker-tools/src/notation-trust/policies/supplychain.json Line 8 in a221025 "trustStores": ["ca:supplychain"], The .NET image signatures include a timestamp countersignature, and the dotnet-docker verification documentation shows configuring both a ca and tsa trust store: https://github.com/dotnet/dotnet-docker/blob/3946d34b71eda376aaeae2e39bf72b6ba3435b5f/documentation/image-signatures.md#L73-L88 We should add the TSA root certificate and reference a tsa trust store in the notation trust policy so that ImageBuilder's signature verification validates the timestamp countersignature. Related: #2079
The --dry-run global CLI option is inconsistent. There are two use cases I'm thinking about: As a container image maintainer, I want to be able to run things like the ACR cleanup pipeline in dry-run mode, against production data, with full authentication -- so that I can be sure what action will be taken before anything is deleted. This is "no side effects mode". As the maintainer of ImageBuilder, I want to have some commands run in public PR validation without authentication to make sure that a pull request hasn't broken our pipelines. This is "no permissions mode" Both are valid but distinct scenarios. Having both contained under the --dry-run flag is inconsistent. I propose that --dry-run should just be #1 or we should change this functionality to be enum-based.
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 dotnet/docker-tools, 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 dotnet/docker-tools acknowledge new external contributions in approximately 19 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.4% were successfully merged into the primary branch.
dotnet/docker-tools has a recorded first-timer success rate of 87.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~19 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 73.0 places dotnet/docker-tools in the Elite tier.
The external pull request merge rate is 87.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dotnet/docker-tools 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 dotnet/docker-tools 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.