Manage your containers
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 13%
Response Time: -
First Timer Success: -
marhkb/pods has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in marhkb/pods respond to incoming external pull requests in approximately 0.0 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 46.6 places marhkb/pods in the B tier.
The external contributor pull request merge rate for marhkb/pods is 12.5%, based on public PR activity from non-core contributors.
marhkb/pods currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in marhkb/pods. Reviews community pull requests with focus on project quality.
Discussions in marhkb/pods focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/marhkb/pods?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (16% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Describe your feature request Related to #783 but I suggest alternative approach. Please add ssh scheme support. It does not need any library support if you use ssh socket forwarding like this: ssh -N -L /tmp/remote-docker.sock:/var/run/docker.sock user@remote-host-ip and then just connect to unix:///tmp/remote-docker.sock I tested this and it works. Would be nice if pods could generate a temp socket name, handle the ssh process lifetime and cleanup after, instead of me manually doing this. In terms of ssh auth you can require user to setup key based auth beforehand if it makes implementation easier since password prompt etc can be tricky.
After creating a container with bind mounts, there is no way except for going to the Kubernetes YAML preview or the very verbose container inspection tab to check which bind mounts have been created. I suggest to add a same type of entry as for reviewing port bindings under the properties: It could also maybe contain links to open local (i.e. host) folders. Full container view Corresponding Kubernetes YAML # Save the output of this file and use kubectl create -f to import # it into Kubernetes. # # Created with podman-5.5.2 # NOTE: If you generated this yaml from an unprivileged and rootless podman container on an SELinux # enabled system, check the podman generate kube man page for steps to follow to ensure that your pod/container # has the right permissions to access the volumes added. --- apiVersion: v1 kind: Pod metadata: creationTimestamp: "2026-09-10T17:58:28Z" labels: app: searxng-pod name: searxng-pod spec: containers: - env: - name: TERM value: x
Reproduction steps Take an action that spawns a notification (e.g. creating a container). The formatting is improperly escaped and isn't interpreted. Environment Pods version: 3.0.0
Hi, Could you please add AppImage support ? It is much easier and system independant than Flatpak. Thanks,
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 marhkb/pods, 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 marhkb/pods acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 12.5% were successfully merged into the primary branch.
marhkb/pods has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 46.6 places marhkb/pods in the Solid tier.
The external pull request merge rate is 12.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, marhkb/pods currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for marhkb/pods 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.