A high-performance multi-language bindings generator for Rust, up to 1,000x faster than UniFFI. Ship Rust libraries that feels native to Python, Swift, Kotlin, and more
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 84%
Response Time: -
First Timer Success: 85%
boltffi/boltffi has a recorded first-timer success rate of 84.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in boltffi/boltffi 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 72.0 places boltffi/boltffi in the S tier.
The external contributor pull request merge rate for boltffi/boltffi is 84.5%, based on public PR activity from non-core contributors.
boltffi/boltffi currently has 12 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in boltffi/boltffi. 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/boltffi/boltffi?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (38% approval). Keep your diff compact for rapid review.
Language C++ Approach We split C++ out of #61 so that issue can stay focused on C. The generated C header already works with C++, but callers still have to manage C handles and allocations themselves. We want generated C++ bindings with values that clean up after themselves, classes with constructors and methods, and clear ownership rules when passing objects to Rust. Follow the adding-a-target guide and build the target from the Binding IR. Reuse the existing transport plans and codec walkers, keeping direct and bulk transfers wherever the shared plans allow them. Before implementing the public API, we need to settle the following using examples of the code a C++ caller would write. The minimum C++ standard and supported compilers. The earlier discussion covered modern C++ and support for older compilers, but no version was agreed on. How owned values, borrowed views, and Rust object handles behave when copied, moved, or destroyed. RAII should release owned resources, and copying mus
Hello everyone! Thank you for your contribution to the ecosystem! It would be nice to have an Elixir support and I'd be happy to help with implementing this
Add a native Node.js target alongside the existing WASM target, not as a replacement. Both backends would be supported, and the consumer picks which one they want to generate for a given build. The WASM target remains fully supported for sandboxed and portable execution, while the native N-API target becomes available as an opt-in backend for server-side projects that need direct OS-level access or native performance characteristics. Relevant discussion here.
Summary Add HarmonyOS NEXT / OpenHarmony platform support to BoltFFI. HarmonyOS is Huawei's OS ecosystem, and HarmonyOS NEXT-style app development is centered around ArkTS. Native interop appears to go through OpenHarmony's NDK / Node-API bridge, where ArkTS/JS can call C/C++ native modules. Rust also has OpenHarmony targets such as aarch64-unknown-linux-ohos, so the rough shape is likely: Rust crate -> OpenHarmony `.so` -> Node-API/native bridge -> ArkTS wrapper This should be treated as a separate platform target, not as Android/Kotlin support. Relationship To Existing Work This is related to #301 because a HarmonyOS backend may be able to share some Node-API infrastructure with a native Node.js target. It is not a duplicate of #301: this issue is specifically about HarmonyOS/OpenHarmony toolchains, packaging, ArkTS-facing bindings, and demo coverage.
React native is extremely popular in the mobile world. Adding support for it would be awesome.
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 boltffi/boltffi, 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 boltffi/boltffi acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 84.5% were successfully merged into the primary branch.
boltffi/boltffi has a recorded first-timer success rate of 84.6%. Repositories ranked Elite 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 72.0 places boltffi/boltffi in the Elite tier.
The external pull request merge rate is 84.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, boltffi/boltffi currently has 12 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for boltffi/boltffi 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.