A Rust algebraic modeling library for solving optimization problems.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
oximo-rs/oximo has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in oximo-rs/oximo 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 7.5 places oximo-rs/oximo in the D tier.
The external contributor pull request merge rate for oximo-rs/oximo is 0.0%, based on public PR activity from non-core contributors.
oximo-rs/oximo currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in oximo-rs/oximo. Reviews community pull requests with focus on project quality.
Discussions in oximo-rs/oximo focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/oximo-rs/oximo?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. The error currently just reports the model kind. Describe the solution you'd like Improve the thiserror message to suggest which backends support that kind (e.g., "MILP is unsupported by Clarabel. Use HiGHS/Gurobi/MOSEK"). Additional context This issue is tagged good first issue specifically to help new contributors get hands-on with the codebase and wants to contribute in the long term. Please do not use AI for this issue.
Is your feature request related to a problem? Please describe. Currently, Clarabel doesn't support Paradiso KKT backends. Describe the solution you'd like Add pardiso variants to ClarabelDirectSolve gated on a new cargo feature. It should follow the existing faer gating pattern. Additional context This issue is tagged good first issue specifically to help new contributors get hands-on with the codebase and wants to contribute in the long term. Please do not use AI for this issue.
Is your feature request related to a problem? Please describe. Currently, we don't support rotated second-order cones. Describe the solution you'd like Extend SocConstraint/SocForm, detection, then translate into each supported backend. Additional context This issue is tagged good first issue specifically to help new contributors get hands-on with the codebase and wants to contribute in the long term. Please do not use AI for this issue.
Is your feature request related to a problem? Please describe. Currently, the LP reader rejects indicator/PWL sections with a generic error. Describe the solution you'd like Improve the UnsupportedLp error message (name the section + point to docs), document supported LP sections in the module docs, and add a test asserting the error for each unsupported keyword. Additional context This issue is tagged good first issue specifically to help new contributors get hands-on with the codebase and wants to contribute in the long term. Please do not use AI for this issue.
Is your feature request related to a problem? Please describe. Currently, the LP writer/reader doesn't have any round-trip tests. Describe the solution you'd like Build models covering senses/bounds/domains/objective names, write to LP string, read back, assert equivalence. Improves confidence in the reader without needing solvers. Additional context This issue is tagged good first issue specifically to help new contributors get hands-on with the codebase and wants to contribute in the long term. Please do not use AI for this issue.
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 oximo-rs/oximo, 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 oximo-rs/oximo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
oximo-rs/oximo has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places oximo-rs/oximo in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, oximo-rs/oximo currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for oximo-rs/oximo 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.