:chart_with_upwards_trend: General purpose hits (page views) counter
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 78%
Response Time: 4d
First Timer Success: 100%
dwyl/hits has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dwyl/hits respond to incoming external pull requests in approximately 89.5 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 56.3 places dwyl/hits in the A tier.
The external contributor pull request merge rate for dwyl/hits is 77.8%, based on public PR activity from non-core contributors.
dwyl/hits currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in dwyl/hits 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/dwyl/hits?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~58 hours (96% approval). Large PRs (>500 lines) take ~430 hours (35% approval). Keep your diff compact for rapid review.
Running: SELECT count(*) AS exact_count FROM hits; We see: With 30M Rows. This query takes 244 seconds. ⏳ Running this query for each hit badge was crashing the server. 💔 But with the hit_count table in place, it's now not a burning issue 🔥 😥 priority-2 because the aggregation isn't crashing the server anymore and we can fix this with time. 🧑💻 🔍 Starting point: https://stackoverflow.com/questions/55018986/postgresql-select-count-query-takes-long-time
Getting the following error: 08:51:46 ** (exit) an exception was raised: 08:51:46 ** (Ecto.MultipleResultsError) expected at most one result but got 2 in query: 08:51:46 from h0 in Hits.HitCount, 08:51:46 (ecto 3.13.6) lib/ecto/repo/queryable.ex:166: Ecto.Repo.Queryable.one/3 08:51:46 (hits 1.7.14) lib/hits_web/controllers/hit_controller.ex:48: HitsWeb.HitController.index/2 08:51:46 (hits 1.7.14) lib/hits_web/controllers/hit_controller.ex:1: HitsWeb.HitController.phoenix_controller_pipeline/2 08:51:46 (hits 1.7.14) lib/hits_web/endpoint.ex:1: HitsWeb.Endpoint.plug_builder_call/2 https://fly.io/apps/hits/monitoring Should be quick to fix in the query. 🔍 BRB. 🧑💻
As noted in #355 the aggregation query (SELECT COUNT(*) FROM hits WHERE repo_id = 123) 💭 takes 2 MINUTES on a table with 30 Million Rows. ⏳ And is the reason the request/query time-out and crashes the server! 💔 So we're implementing hit_count 🆕 which is just an integer counter 1️⃣ to return millisecond responses again. 🏎️ 🏁 🎉 The problem is that we are temporarily ignoring the historical data in the hits table ... 🙄 But the data is not "lost" it's just in stasis. 💭 So ... Todo Create a batch job to go through the hit_count table and update count to reflect the aggregate from hits. 🧑💻 This must be done gradually to avoid crashing the server again. ⚖️ Once all records are updated, we can sunset this data migration script. 🌆 I expect writing the script to take around T1h and running it to take T1w ⏳ (Running the script once per minute to process a single record. 1440 runs per day. 10,000/week) Will work on this immediately after I h
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 dwyl/hits, 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 dwyl/hits acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.8% were successfully merged into the primary branch.
dwyl/hits has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 56.3 places dwyl/hits in the Welcoming tier.
The external pull request merge rate is 77.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dwyl/hits currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for dwyl/hits 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.