Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 01:37 UTC

NVIDIA-NeMo / Gym

Evaluate and improve models and agents using environments

Python · MDXApache-2.0★ 1,055 stars⑂ 228 forkssince Aug 2025View on GitHub ↗
KindMCP serverLibraryNetwork servicehow this is determined

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

93
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.

93
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 79 is calibrated to 93 on the published index scale (record calibration 2026-08-02).

Ownership

NVIDIA-NeMoOrganization
1,350 followers26 public repossince May 2025

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

Package ecosystems

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
31.8/36Commit cadence46/52 weeks with commits
18/18Commit volume801 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year801
human_commit_share
days_since_last_push0
active_weeks_last_year46
How it's scored
27/27Ships releases6 releases published
36/36Release recencylatest release 15 days ago
19.8/27Release cadencea release every ~46 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count6
latest_release_tagv0.4.0
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases46

Community & Adoption

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

83Excellent · 17% of overall
How it's scored
49/60Stars1,055 stars
19.6/25Forks228 forks
5/15Watchers9 watchers
Inputs used
forks228
stars1,055
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
74.8/80Monthly downloads406,438 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesnemo-gym
dependents
ecosystemspypi
total_downloads
monthly_downloads406,438
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?

82Excellent · 23% of overall
How it's scored
48.6/54Bus factor6 contributor(s) cover half of all commits
18.7/22.5Commit distributiontop contributor authored 17% of commits
13.5/13.5Contributor breadth100 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor6
contributors_sampled100
top_contributor_share0.168
How it's scored
20.4/42Issue resolution48% of issues closed
21.2/30PR acceptance872/1,233 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs872
open_issues341
closed_issues321
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.485
closed_unmerged_prs361
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
0/20Verified domainverified-domain status not read for this organization
22.5/25Owner reach1,350 followers of NVIDIA-NeMo
12.7/25Track record26 public repos, account ~1 yr old
Inputs used
followers1,350
owner_typeOrganization
is_verified
owner_loginNVIDIA-NeMo
public_repos26
account_age_days416
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows18 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.nvidia.com/nemo/gym/main/about/
10/10Repository description
10/10Topics10 topics
0/10Wiki
Inputs used
topicsreinforcement-learning, reinforcement-learning-environments, rl-environment, rl-training, gym, agents, benchmarks, environments, evaluation, llm
has_wikino
homepagehttps://docs.nvidia.com/nemo/gym/main/about/
docs_sitehttps://docs.nvidia.com/nemo/gym/main/about/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesuv.lock
manifestsfern/package.json, pyproject.toml
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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.

74Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, resources_servers/terminal_multi_harness/docs/AGENTS.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md, resources_servers/terminal_multi_harness/docs/AGENTS.md
agent_instruction_max_bytes8,267
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
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
54.4/55Manageable file sizes13/1,121 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes166,988
source_files_sampled1,121
oversized_source_files13
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examplesexample, notebooks
Inputs used
example_dirsexample, notebooks
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

1,055GitHub stars
100contributors
801commits, last 12 months
0days since last push
6releases
6bus factor
341open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 29
RegistryPackageVersion constraintManifest
PyPIopenai<=2.7.2pyproject.toml
PyPIanthropic<=0.109.2pyproject.toml
PyPItqdmpyproject.toml
PyPIpydanticpyproject.toml
PyPIpydantic_corepyproject.toml
PyPIdevtoolspyproject.toml
PyPIfastapipyproject.toml
PyPImcp>=1.27,<2pyproject.toml
PyPIitsdangerouspyproject.toml
PyPIuvicornpyproject.toml
PyPIuvlooppyproject.toml
PyPIhydra-corepyproject.toml
PyPIomegaconfpyproject.toml
PyPIrichpyproject.toml
PyPImlflow-skinny>=3.14.0pyproject.toml
PyPImlflow>=3.14.0pyproject.toml
PyPIaiohttp>=3.14.1pyproject.toml
PyPIyappipyproject.toml
PyPIray>=2.55.1pyproject.toml
PyPIpsutilpyproject.toml
PyPIdatasetspyproject.toml
PyPIorjsonpyproject.toml
PyPIurllib3>=2.7.0pyproject.toml
PyPIfonttools>=4.60.2pyproject.toml
PyPIpython-multipart>=0.0.22pyproject.toml
PyPIwandbpyproject.toml
PyPIGitPython>=3.1.50pyproject.toml
PyPIgprof2dotpyproject.toml
PyPIpydotpyproject.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

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.12.0 — full methodology · metrics wiki.

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