An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 76%
Response Time: 20h
First Timer Success: 69%
zalando/skipper has a recorded first-timer success rate of 69.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zalando/skipper respond to incoming external pull requests in approximately 20.3 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 65.3 places zalando/skipper in the A tier.
The external contributor pull request merge rate for zalando/skipper is 75.6%, based on public PR activity from non-core contributors.
zalando/skipper currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in zalando/skipper. 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/zalando/skipper?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 - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (94% approval). Large PRs (>500 lines) take ~97 hours (34% approval). Keep your diff compact for rapid review.
Mirror backend <mirror>, which respond with the incoming may modified request for debugging webhooks or complex configurations References Httpbin ...
Currently zone aware routing does not consider the load at each endpoint. In a scenario where the pods are unevenly distributed in the backend, we provide all endpoints to the load balancer, which leads to imbalanced distribution of traffic. A potential solution could be to implement HAZL
time="2026-09-10T11:47:55Z" level=info msg="Open Policy Agent instance is not ready yet, returning unavailable" bundle-name=somebundle.tar.gz --- FAIL: TestServerResponseFilter (0.06s) --- FAIL: TestServerResponseFilter/Allow_Requests (0.00s) opaserveresponse_test.go:168: Running test for {Allow Requests opaServeResponse somebundle.tar.gz envoy/authz/allow /allow map[] map[] 500} opaserveresponse_test.go:337: Error Trace: /workspace/filters/openpolicyagent/opaserveresponse/opaserveresponse_test.go:337 Error: Not equal: expected: 500 actual : 503 Test: TestServerResponseFilter/Allow_Requests Messages: HTTP status does not match --- FAIL: TestServerResponseFilter/Simple_Forbidden (0.00s) opaserveresponse_test.go:168: Running test for {Simple Forbidden opaServeResponse somebundle.tar.gz envoy/authz/allow /forbidden map[] map[] 403
Is your feature request related to a problem? Please describe. #4033 created a valkey based l2 cache. We should support also redis Describe the solution you would like Redis that has a bit different interface than we need, so likely we need to add in ./net package some redis ring methods to support the required interface.
#4223 introduces a cache that is caching parsed filters and predicates for a single RouteGroup. Sometimes you have a lot of RouteGroups that look very similar with a lot of predicates and filters that we could cache. Think about Method("GET") you have almost N times in every RouteGroup. It does not need to be parsed on every RouteGroup again.
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 zalando/skipper, 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 zalando/skipper acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.6% were successfully merged into the primary branch.
zalando/skipper has a recorded first-timer success rate of 69.2%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 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 65.3 places zalando/skipper in the Welcoming tier.
The external pull request merge rate is 75.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zalando/skipper 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 zalando/skipper 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.