The enterprise gateway for autonomous agents. Identity management, per-channel isolation, credential vault, per-session tamper-evident audit log.
C-Rank Grade: B (Solid) - 72/100
External PR Merge Rate: 94%
Response Time: 1d
First Timer Success: 100%
gebruder/wirken 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 gebruder/wirken respond to incoming external pull requests in approximately 24.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 72.1 places gebruder/wirken in the B tier.
The external contributor pull request merge rate for gebruder/wirken is 94.4%, based on public PR activity from non-core contributors.
gebruder/wirken currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in gebruder/wirken. Ensure PR scope matches issue requirements closely before requesting review.
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/gebruder/wirken?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18: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 ~16 hours (96% approval). Large PRs (>500 lines) take ~119 hours (42% 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 Rust.
To make fuzzing Rust easy
A PostgreSQL 18+ extension for streaming tables with incremental view maintenance, powered by differential dataflow in Rust.
A commissioning tool for pico-fido firmware based hardware keys.
Update (290f13a): the host-bound proxy was replaced with a per-exec sidecar container, removing the host port and with it the firewall dependency in 1b. The acceptance criteria below now pass on a rootful Docker host with ufw default-deny active. This issue stays open until that run is reproduced outside the authoring session. Scope of the verified claim: rootful Docker only. Rootless and Podman are unverified and carry no claim. Per-channel sandbox egress shipped in 511945e with three modes: none (default), allowlist, and open. Two things about the shipped state are wrong or unknown. 1. The allowlist tier is unusable under a rootless runtime allowlist and open need a container runtime whose bridge gateway is a host interface. Under rootless Podman the bridge lives in its own network namespace, the gateway address is not assignable on the host, and the proxy cannot bind it. Podman additionally rejects com.docker.network.bridge.enable_icc outright; its equivalent is isolate. Both paths
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 gebruder/wirken, 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 gebruder/wirken acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.4% were successfully merged into the primary branch.
gebruder/wirken 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 ~1 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 72.1 places gebruder/wirken in the Solid tier.
The external pull request merge rate is 94.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gebruder/wirken 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 gebruder/wirken 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.