eBPF-based Security Observability and Runtime Enforcement
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 60%
Response Time: 3h
First Timer Success: 63%
cilium/tetragon has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cilium/tetragon respond to incoming external pull requests in approximately 2.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 68.9 places cilium/tetragon in the A tier.
The external contributor pull request merge rate for cilium/tetragon is 60.4%, based on public PR activity from non-core contributors.
cilium/tetragon currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in cilium/tetragon 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/cilium/tetragon?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (76% approval). Large PRs (>500 lines) take ~14 hours (27% approval). Keep your diff compact for rapid review.
What happened? How can we reproduce this? Suppose a matchBinaries selector with followChildren: true lists the same path twice. Deleting that policy does not release its mbset ID. Only 64 IDs exist (mbset.MaxIDs), so after 64 add/delete cycles no policy that uses followChildren can load until the agent restarts. Every add and delete in the loop succeeds, so the only sign of the problem is a warning in the agent log. Reproduce Run a standalone agent built from main (no Kubernetes needed): sudo ./tetragon --bpf-lib bpf/objs Save a policy with a repeated followChildren value as dup.yaml: apiVersion: cilium.io/v1alpha1 kind: TracingPolicy metadata: name: mbset-dup-path spec: kprobes: - call: "fd_install" syscall: false selectors: - matchBinaries: - operator: In values: - "/usr/bin/cat" - "/usr/bin/cat" followChildren: true Save the same policy without the repeated value as valid.yaml: apiVersion: cilium.io/v1alpha1 kind: TracingPo
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 cilium/tetragon, 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 cilium/tetragon acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.4% were successfully merged into the primary branch.
cilium/tetragon has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 68.9 places cilium/tetragon in the Welcoming tier.
The external pull request merge rate is 60.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cilium/tetragon 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 cilium/tetragon 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.