CLI tool to discover, manage, and document your IT infrastructure and home lab.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 20%
Response Time: 6h
First Timer Success: -
Timmoth/RackPeek has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Timmoth/RackPeek respond to incoming external pull requests in approximately 5.9 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.5 places Timmoth/RackPeek in the B tier.
The external contributor pull request merge rate for Timmoth/RackPeek is 20.0%, based on public PR activity from non-core contributors.
Timmoth/RackPeek currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
CLI tool to discover, manage, and document your IT infrastructure and home lab.
Collaborative maintainer environment in Timmoth/RackPeek. Reviews community pull requests with focus on project quality.
Discussions in Timmoth/RackPeek 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/Timmoth/RackPeek?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 Monday - 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 ~4 hours (25% approval). Large PRs (>500 lines) take ~28 hours (15% approval). Keep your diff compact for rapid review.
The feature/auto-discovery branch adds rpk discover. It reads your infrastructure and emits RackPeek YAML, so the machine effectively documents itself. It’s safe to run: by default, it only prints the discovered configuration. Nothing is sent anywhere unless you pass --push, and pushes are merged — they never delete or rename anything you’ve written manually. Try it Requires the .NET 10 SDK. git clone https://github.com/Timmoth/RackPeek.git cd RackPeek git checkout feature/auto-discovery https://dotnet.microsoft.com/en-us/download/dotnet/10.0 Run the following commands from the repository root. Discover the current machine Linux/macOS → one System resource: dotnet run --project RackPeek -- discover system Discover Docker containers Creates one Service resource per published container: dotnet run --project RackPeek -- discover docker To discover containers on a remote Docker host: dotnet run --project RackPeek -- discover docker --docker-host tcp://nas.lan:2375 Discover Proxmox
What feature would you like? Add shorter version for commands in CLI, for example allow ap list instead of accesspoints list. Can be either a hardcoded list of allow any unique prefix for the full command, for example access or acc might both work as long as there are no other commands what start with acc. Also, provide tab-completion for known names. For example, if I have 3 servers, "alice", "bob" and "charlie", I could type "servers get c[tab]", this would auto-complete to "charlie" if there are no other servers that start with that previx. What problem does it solve? The need to type full command or unit names when the prefix is already unique. Where would this apply? CLI (rpk commands) Screenshots or mockups (optional) No response
What feature would you like? Add tests that enforce the schema migrations can be applied successfully. Use a similar pattern to the schema validation tests I.E a directory with a bunch of v1 schemas, then match with corresponding files from a v1-2-migration directory. What problem does it solve? Ensures migrations work correctly Where would this apply? Both Screenshots or mockups (optional) No response
Summary When running RackPeek via Docker and using the Web UI’s embedded CLI/terminal, I cannot paste a string of commands (single or multi-line). Standard paste shortcuts either do nothing or only partially paste, making it difficult/impossible to run scripted workflows or bulk command sequences from documentation. Environment Deployment: Docker container (aptacode/rackpeek:latest) using README run/compose approach RackPeek version/tag: latest (please advise if you want a specific release tag tested) Host OS: Windows 10/11 (or Linux/macOS) — fill in Browser: Chrome/Edge/Firefox — fill in version Where the terminal appears: Web UI embedded CLI/terminal (not local rpk binary) Steps to Reproduce Deploy RackPeek in Docker (per README). Open the RackPeek Web UI in a browser. Navigate to the embedded CLI/terminal area. Copy a command string from anywhere (docs, Notepad, README, etc.), for example: echo test ls -la pwd Click into the terminal input area. Attempt to paste
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 Timmoth/RackPeek, 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 Timmoth/RackPeek acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 20.0% were successfully merged into the primary branch.
Timmoth/RackPeek has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 51.5 places Timmoth/RackPeek in the Solid tier.
The external pull request merge rate is 20.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Timmoth/RackPeek currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Timmoth/RackPeek 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.