Cryptography Toolkit
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 82%
Response Time: 1d
First Timer Success: 38%
randombit/botan has a recorded first-timer success rate of 37.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in randombit/botan respond to incoming external pull requests in approximately 24.7 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 69.0 places randombit/botan in the A tier.
The external contributor pull request merge rate for randombit/botan is 82.2%, based on public PR activity from non-core contributors.
randombit/botan currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in randombit/botan. Prompt code reviews with positive guidance for new contributors.
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/randombit/botan?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 Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~119 hours (37% approval). Keep your diff compact for rapid review.
RFC 9846 is an updated version of RFC 8446 that tightens some requirements and clarifies some details. The new revision is fully backward-compatible with the old one, though. Check if we're compliant and fix things as needed. Brownie-points for updating all RFC references in the code (as an independent PR).
#5269 introduced some wrappers for Wycheproof test vectors in Python. They currently run in the nightly tests against the latest test vectors published there. Not all test vectors are currently used and extensions are very welcome. TODO This list might not be complete, see also: testvectors_v1 AEAD KeyWrap ECDH ECDSA EdDSA HKDF MAC ML-DSA ML-KEM RSA Encryption RSA Signing X25519/448 Apart from extending the scope of tested algorithms, it would be really neat if we could make this CPUID aware so that the test vectors are run against all available accelerator implementations.
Sometimes it would be nice to not hard-depend on specific modules. For instance, in TLS: Specialised applications might have a fairly narrow (and predefined) zoo of algorithms that they actually need for TLS within their ecosystem. Nevertheless, TLS info.txt currently pulls in much more than that. For instance, TLS will really need just AEAD, RNG, and perhaps things like HKDF and maybe even SHA. But it could certainly work without Finite-Field Diffie-Hellman, RSA (currently required in TLS 1.2) and GCM in some contexts. On the other hand, this makes the module selection much harder and frustrating for novice users. Often times, missing modules show up only at runtime and are fairly hard to debug. Or catching all relevant platform acceleration modules is tricky and also a maintenance burden when updating. Perhaps an additional <recommended> block of optional module dependencies could help with that? So that one could build along the lines of --minimized-build --enable-modules=tls13 --en
For a while we can use wildcards for module selection. However, the interaction between --enable-modules and --disable-modules isn't very intuitive. For instance, I would assume that --disable-modules=pcurves* --enable-modules=pcurves_brainpool256r1 should disable all pcurves modules except brainpool256r1. That's not true though, because "disable" takes hard precedence over "enable". It is easy to turn that precedence around, but then --minimized-build --enable-modules=pcurves* --disable-modules=pcurves_secp256r1 doesn't work as expected. Personally, I would expect that these selection switches build on top of each other from left to right. I.e. generic (de)selection followed by specific counter-selection should always apply the specific selection on the generic one. Examples (not the current behavior!): --minimized-build --enable-modules=pcurves* --disable-modules=pcurves_brainpool* -> all pcurves except the brainpool ones --disable-modules=pcurves* --enable-modules=pcurves_generic ->
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 randombit/botan, 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 randombit/botan acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.2% were successfully merged into the primary branch.
randombit/botan has a recorded first-timer success rate of 37.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 69.0 places randombit/botan in the Welcoming tier.
The external pull request merge rate is 82.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, randombit/botan currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for randombit/botan 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.