Harbor Satellite
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 15%
Response Time: 15h
First Timer Success: 17%
container-registry/harbor-satellite has a recorded first-timer success rate of 16.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in container-registry/harbor-satellite respond to incoming external pull requests in approximately 14.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 54.3 places container-registry/harbor-satellite in the B tier.
The external contributor pull request merge rate for container-registry/harbor-satellite is 15.4%, based on public PR activity from non-core contributors.
container-registry/harbor-satellite currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in container-registry/harbor-satellite 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/container-registry/harbor-satellite?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (19% approval). Large PRs (>500 lines) take ~70 hours (15% approval). Keep your diff compact for rapid review.
Context Harbor Satellite needs comprehensive user documentation for adoption. Current State README.md with basic info CLAUDE.md for development QUICKSTART.md exists Expected Behavior Documentation covering: Project overview and use cases Getting started guide (satellite + GC setup) Configuration reference API documentation for GC endpoints Architecture diagrams Troubleshooting guide Deployment guides (Docker, Kubernetes, systemd) Location: docs/ directory or separate docs site Value Easier adoption Reduced support burden Clear onboarding path Changes to be Made Create docs/ structure Write getting started guide Document all configuration options Document GC API endpoints Create architecture diagrams Write troubleshooting guide Update README.md with links Files to Create docs/getting-started.md docs/configuration.md docs/api-reference.md docs/architecture.md docs/troubleshooting.md docs/deployment/docker.md docs/deployment/kubernetes.md
Context Satellite needs standard health check endpoints for Kubernetes liveness/readiness probes and monitoring systems. Kuberenetes / Container Runtimes gonna be the consumer - so we need to develop it in a way - that all / most k8s systems could use this as a Precheck before running the pods / containers. Current State Server infrastructure exists at internal/server/ but is not started or used: server.go - App struct manages HTTP server on port 9090 router.go - DefaultRouter with middleware support MetricsRegistrar - Would expose Prometheus at /metrics DebugRegistrar - Would expose pprof at /debug/pprof No health endpoints exist. The server package was scaffolded but never wired into the satellite startup (cmd/main.go and internal/satellite/satellite.go don't start it). For comparison, Ground Control has: GET /ping - returns "pong" GET /health - returns database health status Expected Behavior Start the HTTP server from internal/server/ during satellite startup GET /health (live
Context The satellite uses an embedded Zot registry for local artifact storage. The storage location is defined in the zot_config.storage.rootDirectory field. Current State The default Zot storage path is hardcoded to ./zot (relative to working directory): "zot_config": { "storage": { "rootDirectory": "./zot" } } This is problematic because: Relative paths depend on where the binary is executed from Not suitable for running as a system service No consideration for non-root users Expected Behavior Default storage location should follow XDG conventions for non-root users: ~/.local/share/satellite/registry For root/system service: /var/lib/satellite/registry Configurable via --registry-data-dir flag or REGISTRY_DATA_DIR env var Flag/env should override the zot_config value if provided Value Predictable storage location regardless of working directory Proper defaults for both user and system-level installations Easier integration with systemd services Changes to be Made Add
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 container-registry/harbor-satellite, 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 container-registry/harbor-satellite acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 15.4% were successfully merged into the primary branch.
container-registry/harbor-satellite has a recorded first-timer success rate of 16.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 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 54.3 places container-registry/harbor-satellite in the Solid tier.
The external pull request merge rate is 15.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, container-registry/harbor-satellite 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 container-registry/harbor-satellite 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.