A feature-rich, scalable, Key Management System
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 66%
Response Time: -
First Timer Success: 71%
Cosmian/kms has a recorded first-timer success rate of 71.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Cosmian/kms 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 62.8 places Cosmian/kms in the A tier.
The external contributor pull request merge rate for Cosmian/kms is 66.2%, based on public PR activity from non-core contributors.
Cosmian/kms currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in Cosmian/kms. Ensure PR scope matches issue requirements closely before requesting review.
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/Cosmian/kms?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
The screenshot is self speaking I would even suggest a more "eye catching" for this whole page instead of simply repeating the TOC that's written 500pixels at the left
When trying to destroy a non-revoqued key, this appears: The reason is that the key has not been revoked While the error that appears is (technically, for a crypto POV) correct, it's not very user friendly. I suggest just reverting back to something like "Revoke the key first, please". Not hard to fix.
( I note that this bug might be related to this one #1123 and ideally whoever takes the other one can fix this ) Two problems : Useless line return on header image https://docs.cosmian.com/index.html Take this page for exp : The line return after data makes the background image bigger, waste of space and network data KMIP operation useless line return This applies to all pages that are after : https://docs.cosmian.com/key_management_system/kmip_support/x.html Like this one : https://docs.cosmian.com/key_management_system/kmip_support/_create.html Line returns "get" / "destroy" etc should be removed
https://docs.cosmian.com/ For some reason clicking "/" does not display any search bar (in chrome). Worse in firefox: since that shortcut seems already a firefox embedded searching shortcut ... ? Suggested fix The search bar is where users spend most their life with such a big doc Experience should be conventionnal / easy For example a pretty cummon convention (forgot why) is that Ctrl+K is used as a search shortcut to directly search some specific info in the docs
Original discussion General pupose comment: this file is HUGE and very complicated to read. It does not have a TOC. The redis section appears magically at the start. The content goes on and talks about different topics, and there is a lot of visual anti-patterns that hurt the eyes like orange boxes inside yellow boxes What I suggest deleting the top redis section for now, adding a manual top opening an issue specefically about this matter, referencing this Work seems a bit too much to keep in this PR, I can take it, but as separate issue Originally posted by @HatemMn in #991 (comment) Fixes that should be adressed : TODO Good first issue ! don't hesitate to take it
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 Cosmian/kms, 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 Cosmian/kms acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.2% were successfully merged into the primary branch.
Cosmian/kms has a recorded first-timer success rate of 71.4%. Repositories ranked Welcoming 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 62.8 places Cosmian/kms in the Welcoming tier.
The external pull request merge rate is 66.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Cosmian/kms 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 Cosmian/kms 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.