Core wallet and protocol manager for WDK (Wallet Development Kit) by Tether.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
tetherto/wdk 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 tetherto/wdk 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 7.5 places tetherto/wdk in the D tier.
The external contributor pull request merge rate for tetherto/wdk is 0.0%, based on public PR activity from non-core contributors.
tetherto/wdk does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Core wallet and protocol manager for WDK (Wallet Development Kit) by Tether.
Collaborative maintainer environment in tetherto/wdk. Reviews community pull requests with focus on project quality.
Discussions in tetherto/wdk 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/tetherto/wdk?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 Monday - Wednesday 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 (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Problem When a policy applies, getAccount() returns a proxy that is supposed to hide keyPair and run writes through the policy. The proxy binds leftover functions to the real account so internal this.foo() still works. That also binds Object.prototype.valueOf, so account.valueOf() is the account underneath. Calls on that object skip the policy, and keyPair is readable. Protocol handles use the same proxy, so getSwapProtocol(label).valueOf() is the raw protocol. The tests that assert keyPair is hidden still pass, because they never call valueOf(). https://github.com/tetherto/wdk/blob/main/src/policy/policy-account-proxy.js#L85-L97 https://github.com/tetherto/wdk/blob/main/src/policy/policy-account-proxy.js#L351-L358 https://github.com/tetherto/wdk/blob/main/tests/wdk-policy.test.js#L781-L793 Proposed fix Keep binding the account’s own methods to the real account. Do not bind inherited Object methods (valueOf, and likely toString / toJSON). Then valueOf() stays on the proxy. Cover ac
The WDK library considers a raw seed to be valid ifits length is between 16 and 64 bytes (128 and 512 bits), but BIP39 requires the length to be a multiple of 32 bits. The wdk-wallet library does not perform any raw seed length validation
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 tetherto/wdk, 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 tetherto/wdk acknowledge new external contributions in approximately -. 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.
tetherto/wdk 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 ~-. 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 7.5 places tetherto/wdk 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.
tetherto/wdk 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 tetherto/wdk 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.