STUMPY is a powerful and scalable Python library for modern time series analysis
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 79%
Response Time: <1h
First Timer Success: 67%
stumpy-dev/stumpy has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in stumpy-dev/stumpy respond to incoming external pull requests in approximately 0.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 68.4 places stumpy-dev/stumpy in the A tier.
The external contributor pull request merge rate for stumpy-dev/stumpy is 79.4%, based on public PR activity from non-core contributors.
stumpy-dev/stumpy currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in stumpy-dev/stumpy welcoming community pull requests and bug fixes.
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/stumpy-dev/stumpy?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~0 hours (36% approval). Keep your diff compact for rapid review.
According to the NumPy docs for npt.assert_almost_equal: It is recommended to use one of assert_allclose, assert_array_almost_equal_nulp or assert_array_max_ulp instead of this function for more consistent floating point comparisons. Perhaps, we should migrate our tests accordingly? To Do List Each test file correctly replaces all uses of npt.assert_almost_equal or npt.assert_array_almost_equal with its equivalent npt.assert_allclose (check with grep assert*_almost tests/*) When rtol=0 for npt.assert_allclose, simply omit this paramter and value since this is the default Ensure that npt.assert_allclose(actual, desired) and npt.assert_array_equal(actual, desired) always has the stumpy computed value as "actual" and the naive computation as "desired" Use atol=1.5e-07 rather than atol=1.5*10**-07 Eventually, replace the ugly 1.5*10**-config.STUMPY_TEST_PRECISION with config.STUMPY_TEST_PRECISION = 1.5e-07 (in config.py) Replace comp with cmp Rename naive outputs to ref_ and stu
STUMPY_SEED=462698499 NUMBA_DISABLE_JIT=1 NUMBA_ENABLE_CUDASIM=1 pixi exec --spec black=26.5.1 --spec coverage=7.15.2 --spec dask=2026.7.1 --spec distributed=2026.7.1 --spec flake8=7.3.0 --spec isort=8.0.1 --spec numba=0.66.0 --spec numpy=2.4.6 --spec pandas=3.0.5 --spec polars=1.43.2 --spec pytest=9.1.1 --spec scipy=1.18.0 ./test.sh custom 1 tests/test_motifs.py This test is failing here. It would be good to understand why this is happening and how best to fix it without compromising the test =================================== FAILURES =================================== _________________________________ test_motifs __________________________________ def test_motifs(): T = rng.RNG.rand(64) m = 3 max_motifs = 3 max_matches = 4 max_distance = np.inf cutoff = np.inf # naive # `max_distance` and `cutoff` are hard-coded, and set to np.inf. ref_distances, ref_indices = naive_motifs(T, m, max_motifs, max
STUMPY_SEED=601565739 pixi run tests custom tests/test_stumpi.py This test is failing here. It would be good to understand why this is happening. STUMPY_SEED=601565739 pixi run tests custom tests/test_stumpi.py ============================= test session starts ============================= platform win32 -- Python 3.14.6, pytest-9.1.1, pluggy-1.6.0 rootdir: D:\a\stumpy\stumpy configfile: pytest.ini collected 21 items tests\test_stumpi.py ..............F...... [100%] ================================== FAILURES =================================== _____________ test_stumpi_identical_subsequence_self_join_egress ______________ def test_stumpi_identical_subsequence_self_join_egress(): m = 3 with rng.fix_state(): identical = rng.RNG.rand(8) T = rng.RNG.rand(20) T[1 : 1 + identical.shape[0]] = identical T[11 : 11 + identical.shape[0]] = identical ref_mp = naive.stumpi_eg
STUMPY_SEED=2633420849 NUMBA_DISABLE_JIT=1 NUMBA_ENABLE_CUDASIM=1 pixi run tests custom tests/test_stump.py This test is failing here It would be good to understand why this is happening. For some reason the naive way of computing the matrix profile is different from the performant way. tests\test_stump.py ........F.................... [100%] ================================== FAILURES =================================== _________________ test_stump_identical_subsequence_self_join __________________ def test_stump_identical_subsequence_self_join(): identical = rng.RNG.rand(8) T_A = rng.RNG.rand(20) T_A[1 : 1 + identical.shape[0]] = identical T_A[11 : 11 + identical.shape[0]] = identical m = 3 zone = int(np.ceil(m / 4)) ref_mp = naive.stump(T_A, m, exclusion_zone=zone, row_wise=True) comp_mp = stump(T_A, m, ignore_trivial=True) naive.replace_inf(ref_mp) naive.replace_inf(comp_mp
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 stumpy-dev/stumpy, 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 stumpy-dev/stumpy acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.4% were successfully merged into the primary branch.
stumpy-dev/stumpy has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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.4 places stumpy-dev/stumpy in the Welcoming tier.
The external pull request merge rate is 79.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, stumpy-dev/stumpy currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for stumpy-dev/stumpy 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.