⚓ A collection of high-performance JavaScript tools.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 78%
Response Time: 17h
First Timer Success: 54%
oxc-project/oxc has a recorded first-timer success rate of 53.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in oxc-project/oxc respond to incoming external pull requests in approximately 16.9 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 68.8 places oxc-project/oxc in the A tier.
The external contributor pull request merge rate for oxc-project/oxc is 77.6%, based on public PR activity from non-core contributors.
oxc-project/oxc currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in oxc-project/oxc. 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/oxc-project/oxc?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 Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (96% approval). Large PRs (>500 lines) take ~81 hours (35% approval). Keep your diff compact for rapid review.
Background With the stack of #22907, we finally support rule configuration in the oxlint schema file and Typescript declaration. Problem Some rules are skipped at the moment (see https://github.com/oxc-project/oxc/blob/66fa45ec9d70c6977b045f7f38e0587cdcda15ea/crates/oxc_linter/src/utils/schemars.rs) because: The rule is parsing the configuration manually and is not auto generated by serde_json/schemars crate The rule accepts multiple user configuration format, and resolve them to one "final" config The generated schema/declaration is wrong, see CoPilots comments here #22948 (comment) Task remove only one rule from NO_VERIFIED_VALID_SCHEMA array run just linter-schema-json && just linter-config-ts Verify that the rule configuration follow atleast: Reflects all possible user configuration, see the rule tests or upstream documentation for all possible formats Does not generate wierd TS declarations, like in #22948 (comment) Denies unknown fields, so no [k: string]: unknown; should be
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 oxc-project/oxc, 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 oxc-project/oxc acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.6% were successfully merged into the primary branch.
oxc-project/oxc has a recorded first-timer success rate of 53.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 68.8 places oxc-project/oxc in the Welcoming tier.
The external pull request merge rate is 77.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, oxc-project/oxc 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 oxc-project/oxc 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.