modular service framework to move and transform network packets
C-Rank Grade: S (Elite) - 75/100
External PR Merge Rate: 91%
Response Time: 18h
First Timer Success: 50%
plabayo/rama has a recorded first-timer success rate of 50.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in plabayo/rama respond to incoming external pull requests in approximately 18.1 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 75.4 places plabayo/rama in the S tier.
The external contributor pull request merge rate for plabayo/rama is 90.8%, based on public PR activity from non-core contributors.
plabayo/rama currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in plabayo/rama. 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/plabayo/rama?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (96% approval). Large PRs (>500 lines) take ~87 hours (41% approval). Keep your diff compact for rapid review.
Goal of this ticket is to get the core of wireguard support in Rama finished. Depending on who picks this up it can be done in one or multiple PRs, I'll mention as much in the relevant parts. NOTE: this is mostly a braindump of my thoughts and notes over the last ~ half year thinking about this. It should not be taken as a literal or authorive source on how it should in fact be implemented. rama-wireguard will be a new crate. As such it will also be: be re-exported from the rama crate behind or multiple feature gates have other rama-* dependencies of itself add one or multiple chapters in the rama book to explain WireGuard at a conceptual level be listed in the rama crates ecosystem (The book chapter can honestly be a PR on itself if you do not fancy writing docs) Crate structure wise I see it roughly like this: rama-wireguard/src/ -> /crypto: WireGuardCrypto trait (allows Bring your own Crypto, similar to what we provide in rama-quic, but behind one or multipl
RFC: https://datatracker.ietf.org/doc/html/rfc9421 useful take by Daniel Stenberg: https://daniel.haxx.se/blog/2026/07/27/http-message-signatures-with-curl/ TLDR: http requests and responses can be signed to let the other side of the communication verify that something is unaltered. This is something we also want to support for clients and servers. However it is also important for MITM proxies as those might modify a part that would change the signature. As such we will also need a layer for both directions to ensure we update an existing signatures to the new state prior to sending it through. For the crypto primitives you can ideally make use of rama-crypto. If something is missing let us known or make it part of the PR if contained enough. For this issue @soundofspace and myself (@GlenDC ) can both mentor. No high priority for now as I haven't received any bug reports about it. That said once you start on it do as per usual try to finish it within a matter of days or weeks, rather
While working on my previous PR I noticed that there's no rustfmt configuration regarding import grouping. (Or maybe there's another tool that I've missed?) So I want to ask if it may be possible to adopt following rustfmt settings into rama: group_imports = "StdExternalCrate" imports_granularity = "Crate" In my PR I ended up reformatting key files with these settings to keep convenience of automatic import formatting and in the others I was editing them by hand to avoid unnecessary diffs, which was quite a chore. Maybe I'm just lazy but still it's nice to offload such routine work to a tool 😄 I'm not advocating here for this specific style, but for a way to do it automatically/deterministically.
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 plabayo/rama, 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 plabayo/rama acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.8% were successfully merged into the primary branch.
plabayo/rama has a recorded first-timer success rate of 50.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 hours. 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 75.4 places plabayo/rama in the Elite tier.
The external pull request merge rate is 90.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, plabayo/rama 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 plabayo/rama 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.