Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 14:26 UTC

NVIDIA-NeMo / Automodel

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

PythonApache-2.0★ 943 stars⑂ 305 forkssince May 2025View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

NVIDIA-NeMo/Automodel holds a health index of 97 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on Security (68/100). It was last updated today. 4 contributors account for most of its recent work.

97
overall / 100
Exceptional

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

97
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 85 is calibrated to 97 on the published index scale (record calibration 2026-08-02).

Ownership

NVIDIA-NeMoOrganization · verified domain
1,855 followers28 public repossince May 2025

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPInemo-automodel0.6.020,259817 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

96Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume1,734 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,734
human_commit_share
days_since_last_push0
active_weeks_last_year51
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 17 days ago
19.8/27Release cadencea release every ~49 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv0.6.0
releases_from_tagsno
days_since_latest_release17
mean_days_between_releases49
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

75Good · 17% of overall
How it's scored
48.2/60Stars943 stars
20.7/25Forks305 forks
5/15Watchers9 watchers
Inputs used
forks305
stars943
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
57.4/80Monthly downloads20,259 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesnemo-automodel
dependents
ecosystemspypi
total_downloads
monthly_downloads20,259
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

87Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
17.4/22.5Commit distributiontop contributor authored 23% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 25 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled99
top_contributor_share0.228
How it's scored
28.9/42Issue resolution69% of issues closed
25.2/30PR acceptance2,484/2,956 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs2,484
open_issues195
closed_issues433
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.689
closed_unmerged_prs472
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
23.5/25Owner reach1,855 followers of NVIDIA-NeMo
13.2/25Track record28 public repos, account ~1 yr old
Inputs used
followers1,855
owner_typeOrganization
is_verifiedyes
owner_loginNVIDIA-NeMo
public_repos28
account_age_days473

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 17 days ago
20/20Version history8 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesnemo-automodel
ecosystemspypi
any_deprecatedno
min_days_since_publish17

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows22 workflow(s)
24/24Tests present
16/16Linter config.flake8, .pylintrc, pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.nvidia.com/nemo/automodel/nightly
10/10Repository description
10/10Topics19 topics
10/10Wiki
Inputs used
topicsagent, deepseek-v4, deepseek-v4-flash, finetuning, gemma3, gemma4, glm, gpt-oss, kimi-k3, llama, llama3, llm, minimax-m2, mistral, openai, qwen-38-27b, qwen3, qwen3-next, vlm
has_wikiyes
homepagehttps://docs.nvidia.com/nemo/automodel/nightly
docs_sitehttps://docs.nvidia.com/nemo/automodel/nightly
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 25 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities31 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages163
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:nemo-automodel@0.6.0 runtime dependency closure — what installing the published package pulls in — 163 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

85Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.nvidia.com/llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.nvidia.com/llms.txt
legible_history_share
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes13,383
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapdocs/Makefile, docs/fern/Makefile, nemo_automodel/components/datasets/llm/megatron/Makefile
22/22Automated tests
11/11Lint / format config.flake8, .pylintrc, pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesdocs/Makefile, docs/fern/Makefile, nemo_automodel/components/datasets/llm/megatron/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
53.5/55Manageable file sizes48/1,755 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes202,939
source_files_sampled1,755
oversized_source_files48
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples, notebooks, recipes
Inputs used
example_dirsexamples, notebooks, recipes
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

943GitHub stars
99contributors
1,734commits, last 12 months
0days since last push
8releases
4bus factor
195open issues
PyPIpackage ecosystems

Data collection warnings

  • GraphQL snapshot failed, fell back to REST: GitHub GraphQL error: Something went wrong while executing your query on 2026-09-13T14:25:37Z. Please include `805E:215E9B:14D161F9:143D185C:6AA6B260` when reporting this issue.; Something went wrong while executing your query on 2026-09-13T14:25:37Z. Please include `805E:215E9B:14D161F9:143D185C:6AA6B260` when reporting this issue.
  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 305 ⇿
0Stars
305Forks
8Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

05010015020025030028882025-072026-022026-09
Major 0Minor 6Patch 1

Each point covers 2 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-13 14:26 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 25 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities31 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
PyPIdatasets>=4.0.0pyproject.toml
PyPImegatron-fsdp==0.5.0pyproject.toml
PyPImistral-commonpyproject.toml
PyPIpybind11pyproject.toml
PyPIpyyamlpyproject.toml
PyPItiktokenpyproject.toml
PyPItorch>=2.6.0pyproject.toml
PyPItorchdatapyproject.toml
PyPItransformers==5.15.1pyproject.toml
PyPItorchaopyproject.toml
PyPIflashoptim>=0.1.3pyproject.toml
PyPIquack-kernels==0.6.4pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing pypi:nemo-automodel@0.6.0 pulls in 163 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.