Official Harbor CLI
C-Rank Grade: B (Solid) - 42/100
External PR Merge Rate: 38%
Response Time: 6d
First Timer Success: 33%
goharbor/harbor-cli has a recorded first-timer success rate of 33.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in goharbor/harbor-cli respond to incoming external pull requests in approximately 136.6 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 41.9 places goharbor/harbor-cli in the B tier.
The external contributor pull request merge rate for goharbor/harbor-cli is 38.5%, based on public PR activity from non-core contributors.
goharbor/harbor-cli currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in goharbor/harbor-cli. 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/goharbor/harbor-cli?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 12:00 to 16:00 UTC (12:00 - 16: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 ~89 hours (48% approval). Large PRs (>500 lines) take ~656 hours (17% 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 Go.
Fast passive subdomain enumeration tool.
docker mcp CLI plugin / MCP Gateway
A Matrix-Discord puppeting bridge
harbor-cli/cmd/harbor/root/context/switch.go Line 27 in 6bde8c6 Use: "switch <none|context>", this line should be changed - the word none should be removed from here.
Problem The Harbor CLI currently validates cron expressions in multiple places, for example in: pkg/views/scan-all/update/view.go and cmd/harbor/root/scan_all/update_schedule.go This creates duplicated validation logic and makes future changes harder to maintain. If the validation behavior needs to be updated, it may need to be changed in several files, which increases the risk of inconsistent behavior or missed updates. Proposed Solution Centralize cron expression validation in the utils package. The duplicated validation logic should be moved into a reusable utility function, for example something like: utils.ValidateCronExpression(...) Both the view layer and the command implementation should then use this shared function instead of maintaining their own validation logic. This would make the behavior consistent across the CLI and reduce duplication. Alternatives Considered An alternative would be to keep the current validation logic in each location, but that leaves the code duplica
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 goharbor/harbor-cli, 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 goharbor/harbor-cli acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 38.5% were successfully merged into the primary branch.
goharbor/harbor-cli has a recorded first-timer success rate of 33.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 days+. 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 41.9 places goharbor/harbor-cli in the Solid tier.
The external pull request merge rate is 38.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, goharbor/harbor-cli 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 goharbor/harbor-cli 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.