Prometheus client for node.js
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 62%
Response Time: 5h
First Timer Success: 88%
prometheus/client_js has a recorded first-timer success rate of 87.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in prometheus/client_js respond to incoming external pull requests in approximately 4.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 64.9 places prometheus/client_js in the A tier.
The external contributor pull request merge rate for prometheus/client_js is 61.9%, based on public PR activity from non-core contributors.
prometheus/client_js currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in prometheus/client_js.
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/prometheus/client_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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (77% approval). Large PRs (>500 lines) take ~23 hours (28% approval). Keep your diff compact for rapid review.
A number of PRs have reduced or removed truthiness checks over time, particularly once nullish operators were added to the code. Truthy checks force object coercion, which is both extra clock cycles and additional GC overhead. Even if there aren't many of these left on hot paths, there are for sure a few and the rest still hurt, just not as much. Also nullish and coalescing operators all date back to 14 (one is on 16 but I can't recall which) and we support >=20 so it's overdue. If anyone would like to do a PR to remove most of the rest, I'd like to see that. Please however be aware of the existing open PRs as merge conflicts slow the review process down more than just about anything else. Don't forget to look for ternary operators. There are a few hiding there.
Metrics are being reported in the order they were seen. This is a peculiarity of Object.keys() that persisted when we switched to Maps for metric storage. In conjunction with #689, which will allow people to disable particular default metrics, and #539, which has a side effect of reducing the degree of label reordering between cluster_metrics calls, I think it would be useful from an ergonomics standpoint if someone reordered the defaultMetrics to register the metrics in order of their metric name. Since each of the metrics uses a common prefix for all of its own stats, this should mostly be a matter of rearranging the entries in the object in lib/defaultMetrics.js to order the prefixes alphabetically, and then inspecting the output from one of the examples to verify. Some defaults like heapSizeAndUsed may need a little tweak to make sure the first metric registered is the one with the collect() on it (currently that's total, which is alphabetically last).
I've added some tests to the new functionality in worker.js and cluster.js but for the most part the same code that had no coverage in cluster.js now has no coverage in worker.js metrics.js is also low, particularly for branches. I don't think we need CHANGELOG entries for this work so I'll be ignoring PR errors related to omitting them.
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 prometheus/client_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 prometheus/client_js acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.9% were successfully merged into the primary branch.
prometheus/client_js has a recorded first-timer success rate of 87.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 64.9 places prometheus/client_js in the Welcoming tier.
The external pull request merge rate is 61.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, prometheus/client_js 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 prometheus/client_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.