A CLI wallet library and REPL tool to demo and test the BDK library
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
bitcoindevkit/bdk-cli has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bitcoindevkit/bdk-cli respond to incoming external pull requests in approximately 0.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 29.9 places bitcoindevkit/bdk-cli in the D tier.
The external contributor pull request merge rate for bitcoindevkit/bdk-cli is 0.0%, based on public PR activity from non-core contributors.
bitcoindevkit/bdk-cli currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in bitcoindevkit/bdk-cli. Prompt code reviews with positive guidance for new contributors.
Discussions in bitcoindevkit/bdk-cli 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/bitcoindevkit/bdk-cli?utm_source=github&utm_medium=badge)
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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~2 hours (29% approval). Keep your diff compact for rapid review.
Describe the enhancement The wallet config command stores the configuration information for a wallet in the config.toml file which is then reused on all subsequent wallet operations. However, there is no way to remove/delete a wallet configuration even when the wallet may no longer be needed. Adding a command to delete a saved wallet configuration will help reduce the number of redundant wallet configurations and improve the amount of data saved in the config file. Use case This will allow users to clean up the wallet config file and remove redundant wallet configs.
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 bitcoindevkit/bdk-cli, 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 bitcoindevkit/bdk-cli acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
bitcoindevkit/bdk-cli has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 29.9 places bitcoindevkit/bdk-cli in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bitcoindevkit/bdk-cli 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 bitcoindevkit/bdk-cli 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.