Aim 💫 — An easy-to-use & supercharged open-source experiment tracker.
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
aimhubio/aim 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 aimhubio/aim 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 29.9 places aimhubio/aim in the D tier.
The external contributor pull request merge rate for aimhubio/aim is 0.0%, based on public PR activity from non-core contributors.
aimhubio/aim currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in aimhubio/aim. Reviews community pull requests with focus on project quality.
Discussions in aimhubio/aim 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/aimhubio/aim?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~0 hours (29% approval). Keep your diff compact for rapid review.
Hi, is there a place I can disclose a potential security vulnerability please?
🐛 Bug 64-bit int metrics report incorrectly in the Runs Explorer table if the 31st bit in the value is set. This causes the UI to report an incorrect metric while the metrics graphs and the Aim repo itself will report the correct value. Because the export function in the Runs Explorer view uses the same data from that table, the exported CSVs also contain incorrect values. To reproduce Click for reprex code import os from aim import Repo, Run # byte 3 = 0x3B, high bit clear -> displays correctly as 1,000,000,000 GOOD_VALUE = 1_000_000_000 # byte 3 = 0xB2, high bit SET -> UI displays -1,294,967,296 (off by 2^32 -> negative) BAD_VALUE = 3_000_000_000 repo_path = os.path.dirname(os.path.abspath(__file__)) Repo(repo_path, init=True) run = Run(repo=repo_path, experiment='int64-decoder-bug-demo') run.name = 'int64-decoder-bug-demo' run.track(GOOD_VALUE, name='good_int64', step=0) run.track(BAD_VALUE, name='bad_int64', step=0) run.close() byte3_good = (GOOD_VALUE >> 24) & 0xFF byt
🐛 Bug I updated my codebase to python 3.14. Using pixi which uses conda packages mainly. line 9, in <module> from aim.engine.repo import AimRepo File "/remote/.pixi/envs/default/lib/python3.14/site-packages/aim/engine/repo/__init__.py", line 1, in <module> from aim.engine.repo.repo import AimRepo File "/remote/.pixi/envs/default/lib/python3.14/site-packages/aim/engine/repo/repo.py", line 20, in <module> from aim.engine.repo.run import Run File "/remote/envs/default/lib/python3.14/site-packages/aim/engine/repo/run.py", line 17, in <module> from aim.artifacts.metric import Metric as MetricArtifact File "/remote/.pixi/envs/default/lib/python3.14/site-packages/aim/artifacts/__init__.py", line 1, in <module> from aim.artifacts.map import * File "/remote/envs/default/lib/python3.14/site-packages/aim/artifacts/map.py", line 5, in <module> from aim.artifacts.artifact import Artifact File "/remote/.pixi/envs/default/lib/python3.14/site-packages/aim/artifa
🐛 Bug I've recently started logging some figures each epoch, and am getting intermittent errors where I need to restart Aim or refresh the page until I can get it to load. Error messages in the browser say "Error: Response JSON already consumed" and I've attached one of the full logs below. I'll update this with the other issues as I hit them, there has been a few different types. Today the latest error is preventing me from viewing any runs anymore, it seems to be hitting an exception trying to load run information and everything is green and in progress. It's crashing at the line def list_corrupted_runs(self) -> List[str]: from aim.storage.encoding import decode_path def get_run_hash_from_prefix(prefix: bytes): return decode_path(prefix) container = RocksUnionContainer(os.path.join(self.path, 'meta'), read_only=True) return list(map(get_run_hash_from_prefix, container.corrupted_dbs)) when container is <aim.storage.union.RocksUnio
🐛 Bug I repeatedly get errors in aim regarding "Too many open files". I have tried upping ulimits but it seems that as my database grows the number of open file handlers increases. I am no longer able to use aim-ui without wiping my database clean. To reproduce Have lots of runs? Expected behavior Not crash. Environment Aim Version: 3.29.1 Python version: 3.12 OS: Arch
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 aimhubio/aim, 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 aimhubio/aim acknowledge new external contributions in approximately <1 hour. 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.
aimhubio/aim 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 ~<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 29.9 places aimhubio/aim 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, aimhubio/aim currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for aimhubio/aim 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.