An implementation of the OpenTelemetry specification as a Kotlin Multiplatform Library
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 88%
Response Time: 16h
First Timer Success: 64%
open-telemetry/opentelemetry-kotlin has a recorded first-timer success rate of 64.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-telemetry/opentelemetry-kotlin respond to incoming external pull requests in approximately 15.6 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 open-telemetry/opentelemetry-kotlin in the S tier.
The external contributor pull request merge rate for open-telemetry/opentelemetry-kotlin is 87.5%, based on public PR activity from non-core contributors.
open-telemetry/opentelemetry-kotlin currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in open-telemetry/opentelemetry-kotlin. Prompt code reviews with positive guidance for new contributors.
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/open-telemetry/opentelemetry-kotlin?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 - Thursday 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 ~10 hours (96% approval). Large PRs (>500 lines) take ~75 hours (39% 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 Kotlin.
A modern I/O library for Android, Java, and Kotlin Multiplatform.
A modern open-source VPN client for Android and Android TV, powered by Mihomo. Supports connection chaining, AmneziaWG v3, WireGuard, Hysteria2, subscription imports, connection testing, and a polished Persian/RTL experience.
Pure Android Quick Share implementation without GMS dependency
Implement envar configuration for OTEL_TRACES_SAMPLER and OTEL_TRACES_SAMPLER_ARG: https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/
Implement the OTEL_PROPAGATORS envar: https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/
platformLog() is called in quite a few places where the SdkErrorHandler is probably a more appropriate choice (as errors are being logged). We should update those instances as appropriate. #710 is a pre-requisite (if folks want to avoid merge conflicts)
Implement the following: https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#exporter-selection
Implement envar configuration for OTLP exporters: https://opentelemetry.io/docs/specs/otel/protocol/exporter/
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 open-telemetry/opentelemetry-kotlin, 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 open-telemetry/opentelemetry-kotlin acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.5% were successfully merged into the primary branch.
open-telemetry/opentelemetry-kotlin has a recorded first-timer success rate of 64.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 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 72.1 places open-telemetry/opentelemetry-kotlin in the Elite tier.
The external pull request merge rate is 87.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, open-telemetry/opentelemetry-kotlin 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 open-telemetry/opentelemetry-kotlin 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.