Runtime Security Enforcement System. Workload hardening/sandboxing and implementing least-permissive policies made easy leveraging LSMs (LSM-BPF, AppArmor).
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 39%
Response Time: 2d
First Timer Success: 23%
kubearmor/KubeArmor has a recorded first-timer success rate of 23.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubearmor/KubeArmor respond to incoming external pull requests in approximately 42.2 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 57.2 places kubearmor/KubeArmor in the A tier.
The external contributor pull request merge rate for kubearmor/KubeArmor is 39.4%, based on public PR activity from non-core contributors.
kubearmor/KubeArmor currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in kubearmor/KubeArmor. 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/kubearmor/KubeArmor?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 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~27 hours (49% approval). Large PRs (>500 lines) take ~203 hours (18% approval). Keep your diff compact for rapid review.
Feature Request Short Description Renovate and Dependabot create multiple dependency update PRs, increasing review overhead. Configure each bot to group routine version updates into a single PR. Describe the solution you'd like One grouped version-update PR per bot. Security updates may remain separate.
Bug Report The Codecov badge in the README is showing 0% code coverage.
Bug Report The /KubeArmor/contribution/self-managed-k8s/setup.sh script is not able to install LLVM and Clang on Ubuntu 18.04 after recent changes from #2706 $ sudo apt-get install -y clang-12 llvm-12 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package clang-12 E: Unable to locate package llvm-12 General Information Environment description (GKE, VM-Kubeadm, vagrant-dev-env, minikube, microk8s, ...) - Ubuntu 18.04 Kernel version (run uname -a) - 5.4.0 To Reproduce Run the /KubeArmor/contribution/self-managed-k8s/setup.sh script on Ubuntu 18.04 machine Expected behavior The script should install LLVM and Clang
Feature Request Short Description Automatically rebase open PRs when new changes are pushed to the main branch. Is your feature request related to a problem? Please describe the use case. Open PRs can become outdated as new changes are merged into main. Contributors then need to manually rebase their branches to keep them up to date, which adds unnecessary overhead. Describe the solution you'd like Add a GitHub Action that triggers whenever changes are pushed to main and automatically rebases eligible open PRs targeting main. PRs with conflicts should be skipped and handled manually.
Description Currently, the Trivy scan workflows (ci-trivy-scan.yaml and ci-trivy-scan-ubi.yaml) run on pushes to main and release branches (v*). When ` vulnerabilities are found, the CI run fails, but there is no automated alerting or tracking mechanism. Proposed Solution Enhance the Trivy CI workflows to automatically create and manage GitHub tracking issues when vulnerabilities are detected on main: Automated Issue Creation: Automatically open an issue with labels security and trivy when any component (kubearmor-init, kubearmor, kubearmor-controller, kubearmor-operator) fails the scan. Include affected image list, commit SHA, workflow run link, and the vulnerability report. Deduplication / Noise Reduction: If an open tracking issue already exists, append a comment with the new commit SHA and updated scan results instead of creating duplicate issues on every push. Tasks Update .github/workflows/ci-trivy-scan.yaml Update .github/workflows/ci-trivy-scan-ubi.yaml Ensure tri
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 kubearmor/KubeArmor, 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 kubearmor/KubeArmor acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 39.4% were successfully merged into the primary branch.
kubearmor/KubeArmor has a recorded first-timer success rate of 23.1%. Repositories ranked Welcoming 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 57.2 places kubearmor/KubeArmor in the Welcoming tier.
The external pull request merge rate is 39.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kubearmor/KubeArmor currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kubearmor/KubeArmor 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.