equinor/neqsim - Open Source PR Review Scorecard

NeqSim is a library for calculation of fluid behavior, phase equilibrium and process simulation

C-Rank Grade: S (Elite) - 69/100

External PR Merge Rate: 76%

Response Time: -

First Timer Success: 86%

Frequently Asked Questions

Is equinor/neqsim welcoming to first-time open-source contributors?

equinor/neqsim has a recorded first-timer success rate of 85.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in equinor/neqsim 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.

What does the 69.2 C-Rank™ score (S Tier) represent?

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 69.2 places equinor/neqsim in the S tier.

What is the external contributor pull request merge rate for equinor/neqsim?

The external contributor pull request merge rate for equinor/neqsim is 75.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in equinor/neqsim?

equinor/neqsim does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

equinor
equinor/neqsimS•Elite156
GitHub
Back to Explorer
equinor

equinor/neqsim

156
Active (30d)S•Elite(69/100)Java

NeqSim is a library for calculation of fluid behavior, phase equilibrium and process simulation

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in equinor/neqsim. Reviews community pull requests with focus on project quality.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
75.6%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
85.7%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
5 core
Small core review team
Diagnostic Health HUD
75.6%
Merge Gauge
85.7%
1st-Timer
Community Vibe56/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for equinor/neqsim
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/equinor/neqsim)](https://getmerged.abhishekco.de/equinor/neqsim?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Describe the bug SaturationTemperature.calcSaturationTemperature() and SaturationPressure.calcSaturationPressure() became roughly 20x slower in NeqSim 3.12.0 and remain slow through 3.18.0. The returned values are unchanged — this is purely a performance regression. The bracketing search was rewritten in #2219 ("fix TPflash error"). It now sweeps a fixed full range from a global minimum in coarse steps and never breaks out of the loop when a bracket is found, so every call performs a constant, worst-case number of TPflash evaluations regardless of how close the fluid already is to its saturation boundary: solver swept range step TPflash calls per call, always SaturationTemperature 30 K → 1200 K 10 K ~118 (+ ~20 bisection) SaturationPressure 1 bara → 1000 bara 10 bar ~100 (+ ~20 bisection) Before 3.12.0 the search started from the fluid's current temperature/pressure and walked outward until it crossed the phase boundary — typically a handful of flashes when the flui

📅 Opened Aug 26, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more Java beginner tasks?Explore Java GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for equinor/neqsim

When evaluating whether to contribute to equinor/neqsim, 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 equinor/neqsim acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to equinor/neqsim

01

Is equinor/neqsim welcoming to first-time open-source contributors?

equinor/neqsim has a recorded first-timer success rate of 85.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.2 C-Rank™ score represent?

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 69.2 places equinor/neqsim in the Elite tier.

04

What is the external contributor pull request merge rate for equinor/neqsim?

The external pull request merge rate is 75.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in equinor/neqsim?

equinor/neqsim does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for equinor/neqsim 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.