A toolkit for time series machine learning and deep learning
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 60%
Response Time: 21h
First Timer Success: 61%
aeon-toolkit/aeon has a recorded first-timer success rate of 60.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in aeon-toolkit/aeon respond to incoming external pull requests in approximately 20.6 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 59.4 places aeon-toolkit/aeon in the A tier.
The external contributor pull request merge rate for aeon-toolkit/aeon is 59.8%, based on public PR activity from non-core contributors.
aeon-toolkit/aeon does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in aeon-toolkit/aeon. Maintains strict focus on technical quality and test standards.
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/aeon-toolkit/aeon?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (75% approval). Large PRs (>500 lines) take ~99 hours (27% approval). Keep your diff compact for rapid review.
Describe the bug MERLIN checks this on line 87 for i in range(X.shape[0] - self.min_length + 1): if std(X[i : i + self.min_length]) > AEON_NUMBA_STD_THRESHOLD: warnings.warn( "There is region close to constant that will cause the results " "to be unstable. It is suggested to delete the constant region " "or try again with a longer min_length.", stacklevel=2, ) this check is the wrong way around and will always warn, but warnings are probably supressed in testing. Steps/Code to reproduce the bug run with warnings not supressed Expected results warn on flat Actual results all warnings Suggested fix simple fix, invert test, and also put a break, no point warning repeatedly Versions No response
Describe the issue After #3649 is in, i would like to change the parameter of SAX for the normalization. Currently it is called znormalized and is default to True, which means if it is True then do not znormalize as it is already znormalized which is super confusing :) Suggest a potential alternative/fix I would like to change it and the parameter should be called znormalize and default to True so that it always znormalize the windows (unlike the current setup where default value does not znormalize and user needs to manually set it to False, hence the confusion). Additional context This required deprecation though should fix documentation as well and change the example notebook update tests
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 aeon-toolkit/aeon, 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 aeon-toolkit/aeon acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.8% were successfully merged into the primary branch.
aeon-toolkit/aeon has a recorded first-timer success rate of 60.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 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 59.4 places aeon-toolkit/aeon in the Welcoming tier.
The external pull request merge rate is 59.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
aeon-toolkit/aeon does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for aeon-toolkit/aeon 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.