🏠 Tells you what changed on your server — only what's worth telling. Single Go binary, no database, nothing running on the machines it watches. MCP server built in.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 65%
Response Time: 7h
First Timer Success: 100%
Higangssh/homebutler 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 Higangssh/homebutler respond to incoming external pull requests in approximately 7.4 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 66.5 places Higangssh/homebutler in the A tier.
The external contributor pull request merge rate for Higangssh/homebutler is 64.6%, based on public PR activity from non-core contributors.
Higangssh/homebutler does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in Higangssh/homebutler. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in Higangssh/homebutler 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/Higangssh/homebutler?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (81% approval). Large PRs (>500 lines) take ~36 hours (29% approval). Keep your diff compact for rapid review.
Description Two follow-ups from reviewing #51, deliberately left out of that PR to keep it focused. Both live in the same two files and are worth doing together. inventory show advertises a flag it rejects --filter is registered on scan only (cmd/inventory.go), while show's Short says "Show current server inventory (same as scan)". So: $ homebutler inventory show --filter exposed Error: unknown flag: --filter Both commands already share runInventoryScan, so this is either a one-line registration or a correction to the help text. Registering it on both is probably right — "same as scan" is the promise users read, and there is no reason the filter should not apply. The supported-filter list has two sources of truth RenderTreeFiltered decides what it accepts with a switch (internal/inventory/render.go:76). SupportedFilters() returns a separate slice, and IsSupportedFilter derives from that slice. cmd validates against IsSupportedFilter before collection; RenderTreeFiltered validates ag
Description Add a filter option to homebutler inventory scan so users can quickly see only exposed/public services. This is useful when someone wants to answer: "What is reachable from outside my machine/network?" without reading the full inventory tree. Expected behavior $ homebutler inventory scan --filter exposed Example output: 🏠 Home Network Server demo-lab 🌐 Exposed Ports ├─ :8080/tcp · app-api └─ :8443/tcp · dashboard Scope Add a --filter flag to inventory scan Support at least --filter exposed Only show public/exposed app ports and their related containers/services Keep default inventory scan behavior unchanged Return a clear error for unsupported filter values Implementation hints Start in cmd/inventory.go Filtering can happen after the inventory snapshot is collected Reuse the existing inventory renderers where possible Avoid changing Docker or port scanning behavior in this issue Done when homebutler inventory scan --filter exposed works Unsu
Description Make the common container troubleshooting questions answerable through homebutler, without adding a general command-execution primitive. This issue originally asked for homebutler docker exec <container> -- <cmd>. That scope is withdrawn — see the comment below for the reasoning. The short version is that the two examples it was motivated by are both answerable from the host, and arbitrary exec would contradict what the rest of the tool promises. Expected behavior $ homebutler docker top app-api PID USER COMMAND 1 root nginx: master process nginx -g daemon off; 31 nginx nginx: worker process $ homebutler docker inspect app-api 📦 app-api Image nginx:1.27-alpine State running (up 4d) Restart unless-stopped · 0 restarts Ports 0.0.0.0:8080 → 80/tcp Mounts /srv/app/data → /data (rw) Networks bridge (172.17.0.4) Health healthy homebutler docker top app-api --json homebutler docker inspect app-api --json Sc
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 Higangssh/homebutler, 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 Higangssh/homebutler acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.6% were successfully merged into the primary branch.
Higangssh/homebutler 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 ~7 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 66.5 places Higangssh/homebutler in the Welcoming tier.
The external pull request merge rate is 64.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Higangssh/homebutler does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for Higangssh/homebutler 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.