OpenTelemetry JavaScript Client
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 49%
Response Time: 9h
First Timer Success: 50%
open-telemetry/opentelemetry-js has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-telemetry/opentelemetry-js respond to incoming external pull requests in approximately 8.8 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 60.3 places open-telemetry/opentelemetry-js in the A tier.
The external contributor pull request merge rate for open-telemetry/opentelemetry-js is 49.0%, based on public PR activity from non-core contributors.
open-telemetry/opentelemetry-js currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
OpenTelemetry JavaScript Client
Active maintainer team in open-telemetry/opentelemetry-js 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/open-telemetry/opentelemetry-js?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (61% approval). Large PRs (>500 lines) take ~42 hours (22% approval). Keep your diff compact for rapid review.
@opentelemetry/sdk-trace-node is being removed in favor of @opentelemetry/sdk-trace. Goal is to remove the package and update documentation to reflect that @opentelemetry/sdk-trace should now be used instead (or @opentelemetry/sdk-node if env var config is desired). This issue is done when: package has been removed (#7094) usages of the package have been migrated to @opentelemetry/sdk-trace or @opentelemetry/sdk-node (here and in the contrib repo) also remove the re-export from @opentelemetry/sdk-node (see #5461). The re-export from sdk-node was already removed in #7079 recently. docs updated (SDK 3.0 migration, and other documentation here or in the https://github.com/open-telemetry/opentelemetry-js-contrib repo has been updated) (trent-update) docs updated in opentelemetry.io user docs
Background Follow-up from PR #6293 review discussion: #6293 (comment) After migrating the build to tsdown/nx, the unit-test workflow rebuilds each package per Node.js version in the matrix. This pushed CI build time from ~32s to ~60s, repeated for every Node.js version (8 entries), since nothing is shared across matrix legs. Proposal Leverage the nx compilation cache so we build once and reuse the cached output across all versions of the test matrix, rather than recompiling per leg. opentelemetry-js-contrib already does this: https://github.com/open-telemetry/opentelemetry-js-contrib/blob/2b3c0f7298727d8ac80dba95c89fd6dd7c6fe2f0/.github/workflows/test.yml#L12 The expectation is to keep the ~60s build once and have the whole matrix reuse it, instead of paying the compile cost on each leg. Notes Deferred from #6293 as a non-blocking follow-up.
https://opentelemetry.io/docs/specs/otel/trace/sdk/#probabilitysampler ProbabilitySampler was added to the spec in open-telemetry/opentelemetry-specification#4627 See #6503 (comment) for a recent motivator for this. See related #6540 for renaming the related Composable sampler.
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-js, 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-js acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 49.0% were successfully merged into the primary branch.
open-telemetry/opentelemetry-js has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 60.3 places open-telemetry/opentelemetry-js in the Welcoming tier.
The external pull request merge rate is 49.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, open-telemetry/opentelemetry-js currently has 2 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-js 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.