A Rust HAL implementation for the CH32V0, CH32V1, CH32V2, CH32V3, CH32X0, CH32L1 family, with Embassy framework support and compatible with embedded-hal.
C-Rank Grade: B (Solid) - 57/100
External PR Merge Rate: 100%
Response Time: 3d
First Timer Success: 100%
ch32-rs/ch32-hal has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ch32-rs/ch32-hal respond to incoming external pull requests in approximately 62.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 56.9 places ch32-rs/ch32-hal in the B tier.
The external contributor pull request merge rate for ch32-rs/ch32-hal is 100.0%, based on public PR activity from non-core contributors.
ch32-rs/ch32-hal currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in ch32-rs/ch32-hal. Reviews community pull requests with focus on project quality.
Discussions in ch32-rs/ch32-hal 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/ch32-rs/ch32-hal?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~41 hours (96% approval). Large PRs (>500 lines) take ~299 hours (45% approval). Keep your diff compact for rapid review.
Chips like CH32V203C8T6 support USB host mode via USBFS (separate from OTG FS), but support seems to not be implemented at this time.
Async Uart that hasn't been split into UartRx and UartTx is missing async read and write functions, only blocking ones are present. Blocking read/write inside unsplit 'Uart' meanwhile are rerouted to inner rx/tx parts. So it should be possible to do the same for async read/write. Also, async UartTx is missing flush, while the blocking version has it. From a quick look at the code, it seems that blocking_write returns when the input buffer is fully consumed, but the last byte might not be fully sent yet, which makes blocking_flush necessary. Async write seems to finish polling also when the buffer is fully consumed, not when all bits are sent(correct me if I'm wrong here). That would suggest async flush should also be present. Implementing that would be more difficult (enabling TXE interrupt, creating a new AtomicWaker for it, adding TXE to the interrupt handler, etc.) I could try making a PR for this, but I only have a CH32V003 to test it on
These are the issues I met when adding the support for keeping date and time to ch32v203 1- hal::init(config) won't initialize the low speed oscillator; discarding the provided LsConfig . 2- R32_PWR_CTLR isn't exposed by the PAC to enable "Backup Domain Write" 3- The low speed oscillator always resets after flashing with wlink, but the backup registers are preserved. That's why I'm not using the backup registers for detecting first initialization. The code below isn't polished yet and lacks next second interrupt. At least, it provides some methods for reading and updating current date and time // rtc/mod.rs mod rtc_raw; mod rtc; pub use rtc::*; mod rtc_init; pub use rtc_init::*; // rtc/rtc.rs use hal::pac::RTC; use heapless::format; // this is only needed for formatting date and time use time::{Date, Month, Time, UtcDateTime}; use embassy_sync::lazy_lock::LazyLock; const REFERENCE_YEAR: i32 = 2020; pub static REFERENCE_DATE_TIME: LazyLock<UtcDateTime> = LazyLock::new(|| { let r
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 ch32-rs/ch32-hal, 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 ch32-rs/ch32-hal acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
ch32-rs/ch32-hal has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 56.9 places ch32-rs/ch32-hal in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ch32-rs/ch32-hal currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ch32-rs/ch32-hal 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.