⚡️A terminal-based battery and energy monitor for macOS and Linux.
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: 100%
jordond/jolt has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jordond/jolt respond to incoming external pull requests in approximately 0.0 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 51.6 places jordond/jolt in the B tier.
The external contributor pull request merge rate for jordond/jolt is 100.0%, based on public PR activity from non-core contributors.
jordond/jolt currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in jordond/jolt. Reviews community pull requests with focus on project quality.
Discussions in jordond/jolt focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/jordond/jolt?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (45% approval). Keep your diff compact for rapid review.
Hi! Thanks for jolt it's truly an awesome tool I use every day :) It'd be cool if the Brewfile for jolt would define a system service which can be started for jolt's daemon mode. Here's an example for another popular TUI-tool (atuin): https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/a/atuin.rb#L27-L32 With that in place, users can auto-start the daemon when they log in without having to do so manually. Here's a quick snippet of atuin's server as managed by brew: ❯ brew services Name Status User File atuin started jlf ~/Library/LaunchAgents/homebrew.mxcl.atuin.plist ❯ brew services info atuin atuin (homebrew.mxcl.atuin) Running: ✔ Loaded: ✔ Schedulable: ✘ User: jlf PID: 46239 I am still trying to maximize my use of jolt, so perhaps I've misunderstood the daemon mode, but starting it manually to keep historical timings is error prone, for this user at least. ;) ❯ ps -ef | grep jolt 501 980 1 0 Thu10PM ?? 12:16.02 /opt/hom
Came across this utility, it looks great! I'd love to replace battop with this for my system. I ran this on Arch, compiled from source. However, there are some issues present: Most importantly, the shown total power draw is way too low. Does it only add CPU+GPU power draw together? That doesn't reflect total system power draw, and also means the forecast is way off. In the image below you can see the power draw as reported by battop as compared to that of jolt. Its time to empty closely matches how long my laptop lasts on battery, so I assume this total is correct, while jolt only reports about half of that total. System reported as an unknown macOS. This is fixed in #126. (screenshot is made from that branch) Status title is right-aligned, while all other tab titles are left-aligned. Let me know if you need additional information :)
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 jordond/jolt, 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 jordond/jolt acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
jordond/jolt has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 51.6 places jordond/jolt in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jordond/jolt 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 jordond/jolt 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.