DragonOS is an operating system developed from scratch using Rust, with Linux compatibility. It is designed for **Serverless** scenarios.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 83%
Response Time: 1d
First Timer Success: 55%
DragonOS-Community/DragonOS has a recorded first-timer success rate of 54.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DragonOS-Community/DragonOS respond to incoming external pull requests in approximately 27.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 67.6 places DragonOS-Community/DragonOS in the A tier.
The external contributor pull request merge rate for DragonOS-Community/DragonOS is 83.0%, based on public PR activity from non-core contributors.
DragonOS-Community/DragonOS currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in DragonOS-Community/DragonOS. 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/DragonOS-Community/DragonOS?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (96% approval). Large PRs (>500 lines) take ~130 hours (37% approval). Keep your diff compact for rapid review.
Background DragonOS's device model relies heavily on sysfs symbolic links to express relationships between drivers, devices, and subsystems (e.g. device → driver, driver → subsystem). The creation path (SysFS::create_link) is fully implemented, but the corresponding removal path (SysFS::remove_link) is still a todo!(). This means device unbind, driver unload, and error-rollback flows all silently fail to clean up the symlinks they create, leaving stale entries in sysfs. Current Status SysFS::create_link() — implemented (kernel/src/filesystem/sysfs/symlink.rs) SysFS::remove_link() — todo!("sysfs remove link") (line 42 of the same file) Multiple callers already exist and are waiting on this implementation: kernel/src/driver/base/device/mod.rs (lines 760, 764, 916) kernel/src/driver/base/device/driver.rs (lines 245, 250) kernel/src/driver/base/device/dd.rs (lines 484, 496) Code Entry Points Primary files: kernel/src/filesystem/sysfs/symlink.rs — add the implementation here
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 DragonOS-Community/DragonOS, 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 DragonOS-Community/DragonOS acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.0% were successfully merged into the primary branch.
DragonOS-Community/DragonOS has a recorded first-timer success rate of 54.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 67.6 places DragonOS-Community/DragonOS in the Welcoming tier.
The external pull request merge rate is 83.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, DragonOS-Community/DragonOS currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for DragonOS-Community/DragonOS 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.