stan-dev/math - Open Source PR Review Scorecard

The Stan Math Library is a C++ template library for automatic differentiation of any order using forward, reverse, and mixed modes. It includes a range of built-in functions for probabilistic modeling, linear algebra, and equation solving.

C-Rank Grade: A (Welcoming) - 58/100

External PR Merge Rate: 68%

Response Time: 2d

First Timer Success: 83%

Frequently Asked Questions

Is stan-dev/math welcoming to first-time open-source contributors?

stan-dev/math has a recorded first-timer success rate of 83.3%. Repositories ranked A 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 stan-dev/math respond to incoming external pull requests in approximately 46.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 58.4 C-Rank™ score (A 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 58.4 places stan-dev/math in the A tier.

What is the external contributor pull request merge rate for stan-dev/math?

The external contributor pull request merge rate for stan-dev/math is 68.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in stan-dev/math?

stan-dev/math currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

stan-dev
stan-dev/mathAWelcoming832
GitHub
Back to Explorer
stan-dev

stan-dev/math

832
AWelcoming(58/100)C++

The Stan Math Library is a C++ template library for automatic differentiation of any order using forward, reverse, and mixed modes. It includes a range of built-in functions for probabilistic modeling, linear algebra, and equation solving.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in stan-dev/math.

Top PR Submission Do's

  • Add unit tests with >80% coverage for modified code paths
  • Use conventional commit messages and clean branch names
  • Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without referencing an existing issue
  • Do not mix refactoring and feature logic into a single commit
  • Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
68.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
13 core
Highly collaborative maintainer core
Diagnostic Health HUD
68.1%
Merge Gauge
83.3%
1st-Timer
Community Vibe52/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Reported by @sims1253 for bernoulli_logit_lpmf here and bernoulli_logit_glm_lpmf here. Here are some tests that would fail if inserted into math/test/unit/math/mix/prob/bernoulli_logit_glm_lpmf_test.cpp Line 4 in 344d716 TEST_F(AgradRev, mathMixScalFun_bernoulli_logit_glm_lpmf) { // internal cutoff for extreme values const double cutoff = 20; Eigen::MatrixXd x_one(1, 1); x_one << 1.0; Eigen::Matrix<double, Eigen::Dynamic, 1> beta_one(1, 1); beta_one << (cutoff + 5); stan::test::ad_tolerances tols; tols.gradient_grad_ = 1e-6; stan::test::expect_ad(tols, f(0), x_one, 0.0, beta_one); stan::test::expect_ad(tols, f(1), x_one, 0.0, beta_one); stan::test::expect_ad(tols, f(2), x_one, 0.0, beta_one); Eigen::Matrix<double, Eigen::Dynamic, 1> beta_flipped = beta * -1; stan::test::expect_ad(tols, f(0), x_one, 0.0, beta_flipped); stan::test::expect_ad(to

📅 Opened Aug 24, 2026💬 0 comments
Quality: 90/100Contribute

For example, in prim/fun/square.hpp. Note that some care must be taken to avoid changing the rounding behavior by casting the input before multiplying With default toolchain settings (gcc/clang default to -fmath-errno), std::pow must set errno on domain/range/overflow errors, so the optimizer cannot rewrite it to a multiply in general. glibc's pow is a branchy multi-path implementation where x * x is one instruction. Originally posted by @sims1253 in #3368

📅 Opened Aug 24, 2026💬 10 comments
Quality: 90/100Contribute

The code was generated by chatgpt sol. The math patch code is attached. The algorithm is from https://dl.acm.org/doi/10.1145/3423597. @WardBrian this is the solver we discussed about. functions { // Replace this body to prototype a different scalar equation f(x, ...)=0. // This example solves x^3 - theta[1] = 0. real itp_residual(real x, vector theta, array[] real x_r, array[] int x_i) { return x * x * x - theta[1]; } int itp_n_half(real width, real x_tolerance, int max_num_steps) { int n_half = 0; real bisection_width = 2.0 * x_tolerance; while (bisection_width < width) { if (n_half >= max_num_steps) { reject("solve_itp_prototype: max_num_steps is too small for the ", "requested bracket width and x_tolerance"); } bisection_width *= 2.0; n_half += 1; } return n_half; } // Overflow-resistant regula-falsi point for opposite-signed fa and fb. real itp_false_position(real a, real b

📅 Opened Aug 21, 2026💬 1 comment
Quality: 90/100Contribute

To facilitate working with the sum-to-zero constraint in multivariate contexts, it would be valuable to be able to specify not only individual sum_to_zero_vectors but also matrices for which all rows or all columns are constrained to sum to zero. To my knowledge, there is no universally standard name for such a mathematical object (nor to Claude's knowledge, which only produced a list of suggestions), but for the sake of starting a conversation, I would propose something like row_centered_matrix and col_centered_matrix (and perhaps row_centred_matrix and col_centred_matrix as aliases for spelling-dialect neutrality). The primary use case for me would be hierarchical modelling with correlated multivariate random effects, e.g., random-slopes models or multivariate item-response models. To reduce problems with funnel geometries during sampling, it can be wise to write such models using ‘raw’ parameters with standard normal priors and then construct the actual parameters in the transfo

📅 Opened Aug 18, 2026💬 3 comments
Quality: 90/100Contribute

I would rather write is_odd(n) than n % 2 == 1 or more obscure n % 2.. Same for is_even(n) vs. n % 2 == 0 or more obscurely !(n % 2). This is about the simplest pair of functions to add because they don't need overloads for different scalar types and don't have derivatives. It would be great if they could be vectorized over arrays of any shape to return an array of the same shape with 0/1 values based on whether each element is odd or not. This should then be added to the Stan language and doc.

📅 Opened Jul 20, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more C++ beginner tasks?Explore C++ 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 stan-dev/math

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

Frequently Asked Questions - Contributing to stan-dev/math

01

Is stan-dev/math welcoming to first-time open-source contributors?

stan-dev/math has a recorded first-timer success rate of 83.3%. Repositories ranked Welcoming 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 58.4 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 58.4 places stan-dev/math in the Welcoming tier.

04

What is the external contributor pull request merge rate for stan-dev/math?

The external pull request merge rate is 68.1%. 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 stan-dev/math?

Yes, stan-dev/math currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for stan-dev/math 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.