NVIDIA-NeMo/Automodel - Open Source PR Review Scorecard

🚀 Pytorch Distributed native training library for LLMs/VLMs with OOTB Hugging Face support

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

External PR Merge Rate: 75%

Response Time: -

First Timer Success: 64%

Frequently Asked Questions

Is NVIDIA-NeMo/Automodel welcoming to first-time open-source contributors?

NVIDIA-NeMo/Automodel has a recorded first-timer success rate of 64.0%. 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 NVIDIA-NeMo/Automodel 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 71.7 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 71.7 places NVIDIA-NeMo/Automodel in the S tier.

What is the external contributor pull request merge rate for NVIDIA-NeMo/Automodel?

The external contributor pull request merge rate for NVIDIA-NeMo/Automodel is 74.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in NVIDIA-NeMo/Automodel?

NVIDIA-NeMo/Automodel currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

NVIDIA-NeMo
NVIDIA-NeMo/AutomodelS•Elite1.0k
GitHub
Back to Explorer
NVIDIA-NeMo

NVIDIA-NeMo/Automodel

1,010
Active (30d)S•Elite(72/100)Python

🚀 Pytorch Distributed native training library for LLMs/VLMs with OOTB Hugging Face support

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.9/10
Patience Score
8.4/10
Nitpick Rate
20%

Highly welcoming maintainers in NVIDIA-NeMo/Automodel. Prompt code reviews with positive guidance for new contributors.

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
74.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
46 core
Highly collaborative maintainer core
Diagnostic Health HUD
74.6%
Merge Gauge
64.0%
1st-Timer
Community Vibe49/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Is your feature request related to a problem? Please describe. See here see https://github.com/marcelroed/gigatoken#gigatoken for context ; Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.

📅 Opened Jul 22, 2026💬 6 comments
Quality: 40/100Contribute

Context Follow-up to AM-730. The successful scoped release CI run for nemotron_nano_v3_singlegpu_lora proved the AM-730 activation-checkpointing fix, but loading the 58.82 GiB base checkpoint took 570.10 seconds: Disk read: 5.78 seconds HF-to-AutoModel state conversion and model copy (currently logged together as distribute): 564.32 seconds Overall effective rate: 0.10 GiB/s The job used an exclusive EOS node with 224 allocated CPUs, while Slurm reported CPUs/Task=1. The run did not log process affinity or PyTorch intra-op/inter-op thread counts, so a one-CPU restriction is a hypothesis, not an established root cause. The current path CPU-merges thousands of split expert tensors into grouped MoE weights, performs repeated garbage collection/cache cleanup, and then copies the full state into the single-GPU model. The JoC harness supports CPUS_PER_TASK, but AutoModel's recipe CI generator does not currently expose it. Investigation Log os.sched_getaffinity(0), torch.get_num_threads(),

📅 Opened Jul 21, 2026💬 1 comment
Quality: 50/100Contribute

https://huggingface.co/XiaomiMiMo/MiMo-V2.5-Pro

📅 Opened Jun 9, 2026💬 1 comment
Quality: 15/100Contribute

Is your feature request related to a problem? Please describe. AM uses .map(fn) to transform datasets (e.g., apply template, tokenize etc). Unfortunately, this happens during startup and runs over the whole dataset. In addition, the current caching functionality often fails, incurring additional delay on repeated runs. 2026-04-20 12:09:22 | INFO | httpx | HTTP Request: HEAD https://huggingface.co/akoumpa/Devstral-Small-2-24B-Instruct-2512-BF16/resolve/main/config.json "HTTP/1.1 307 Temporary Redirect" 2026-04-20 12:09:22 | INFO | httpx | HTTP Request: HEAD https://huggingface.co/api/resolve-cache/models/akoumpa/Devstral-Small-2-24B-Instruct-2512-BF16/6d6f531753869fcd8cbbaefa7ee94b93966d2d04/config.json "HTTP/ 1.1 200 OK" 2026-04-20 12:09:23 | INFO | nemo_automodel._transformers.auto_tokenizer | Using custom tokenizer MistralCommonBackend for model type 'mistral3' 2026-04-20 12:09:23 | INFO | httpx | HTTP Request: GET https://huggingface.co/api/models/akoumpa/Devstral-Small-2-24B-Instru

📅 Opened Apr 20, 2026💬 2 comments
Quality: 30/100Contribute

Describe the bug In particular for #1631, after fixing the tied weights issue, I run into another issue where the default collator was creating a "padding_mask" although the model is unable to consume it, thus crashing the run. 1631 included a filtering step to remove the padding_mask, but it would be better not to have to do any filtering, as it pollutes/complicates the code. Steps/Code to reproduce bug Run the yaml that I have attached to 1631 Expected behavior Run without crashing / having to filter the batch. Additional context Add any other context about the problem here.

📅 Opened Mar 31, 2026💬 3 comments
Quality: 30/100Contribute
Looking for more Python beginner tasks?Explore Python 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 NVIDIA-NeMo/Automodel

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

Frequently Asked Questions - Contributing to NVIDIA-NeMo/Automodel

01

Is NVIDIA-NeMo/Automodel welcoming to first-time open-source contributors?

NVIDIA-NeMo/Automodel has a recorded first-timer success rate of 64.0%. 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 71.7 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 71.7 places NVIDIA-NeMo/Automodel in the Elite tier.

04

What is the external contributor pull request merge rate for NVIDIA-NeMo/Automodel?

The external pull request merge rate is 74.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 NVIDIA-NeMo/Automodel?

Yes, NVIDIA-NeMo/Automodel currently has 5 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 NVIDIA-NeMo/Automodel 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.