Open-source observability for your GenAI or LLM application, based on OpenTelemetry
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 17%
Response Time: 18h
First Timer Success: 3%
traceloop/openllmetry has a recorded first-timer success rate of 2.9%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in traceloop/openllmetry respond to incoming external pull requests in approximately 17.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 47.9 places traceloop/openllmetry in the B tier.
The external contributor pull request merge rate for traceloop/openllmetry is 16.6%, based on public PR activity from non-core contributors.
traceloop/openllmetry currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (80% positive review sentiment). Active code reviews with constructive guidance for new contributors in traceloop/openllmetry.
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/traceloop/openllmetry?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (21% approval). Large PRs (>500 lines) take ~86 hours (15% approval). Keep your diff compact for rapid review.
Which component is this feature for? AlephAlpha Instrumentation 🔖 Feature description Hi, This project is very interesting and useful for LLM observability. I think adding a simple beginner-friendly example (e.g., tracking a basic LLM call step-by-step) would help new users understand how to get started quickly. I’d be happy to contribute to this if it’s helpful. Thanks! 🎤 Why is this feature needed ? Currently, new users who are not familiar with LLM observability may find it difficult to understand how to get started with tracing. While the documentation is helpful, a simple step-by-step beginner example demonstrating how to trace a basic LLM call would make onboarding much easier. This would help users quickly understand how the library works in practice and reduce the learning curve, especially for those new to observability concepts. ✌️ How do you aim to achieve this? I plan to create a simple, beginner-friendly example demonstrating LLM tracing. This would include:
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 traceloop/openllmetry, 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 traceloop/openllmetry acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.6% were successfully merged into the primary branch.
traceloop/openllmetry has a recorded first-timer success rate of 2.9%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 47.9 places traceloop/openllmetry in the Solid tier.
The external pull request merge rate is 16.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, traceloop/openllmetry 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 traceloop/openllmetry 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.