Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 15:16 UTC

NVIDIA-NeMo / Gym

Evaluate and improve models and agents using environments

Python · MDXApache-2.0★ 1,179 stars⑂ 322 forkssince Aug 2025View on GitHub ↗
KindCommand-line toolLibraryMCP serverNetwork servicehow this is determined

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

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

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

Ownership

NVIDIA-NeMoOrganization · verified domain
1,840 followers28 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?

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 1,186 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year1,186
human_commit_share1
days_since_last_push0
active_weeks_last_year51

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 9 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~37.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tagv0.6.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases37.2

Community & Adoption

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

85Excellent · 17% of overall
How it's scored
49.8/60Stars — 1,179 stars
20.9/25Forks — 322 forks
4.7/15Watchers — 8 watchers
Inputs used
forks322
stars1,179
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
74.3/80Monthly downloads — 375,840 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnemo-gym
dependents—
ecosystemspypi
total_downloads—
monthly_downloads375,840
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?

86Excellent · 23% of overall
How it's scored
51.3/54Bus factor — 7 contributor(s) cover half of all commits
19.4/22.5Commit distribution — top contributor authored 14% of commits
13.5/13.5Contributor breadth — 100 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor7
contributors_sampled100
top_contributor_share0.139
How it's scored
20.2/42Issue resolution — 48% of issues closed
21.9/30PR acceptance — 1,399/1,913 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs1,399
open_issues493
closed_issues459
prs_merged_7d36
prs_decided_7d56
prs_merged_30d39
prs_decided_30d59
issue_closed_ratio0.482
closed_unmerged_prs514
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
23.5/25Owner reach — 1,840 followers of NVIDIA-NeMo
13.2/25Track record — 28 public repos, account ~1 yr old
Inputs used
followers1,840
owner_typeOrganization
is_verifiedyes
owner_loginNVIDIA-NeMo
public_repos28
account_age_days470

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 1 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnemo-gym
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 20 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.nvidia.com/nemo/gym/main/about/
10/10Repository description
10/10Topics — 10 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_dirno
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfiles — uv.lock
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesuv.lock
manifestsfern/package.json, pyproject.toml
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno

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.

79Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, resources_servers/terminal_multi_harness/docs/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.nvidia.com/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.nvidia.com/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md, resources_servers/terminal_multi_harness/docs/AGENTS.md
agent_instruction_max_bytes9,949
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.17
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
53.9/55Manageable file sizes — 40/1,984 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes265,995
source_files_sampled1,984
oversized_source_files40
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — example, examples, notebooks
Inputs used
example_dirsexample, examples, notebooks
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

1,179GitHub stars
100contributors
1,186commits, last 12 months
0days since last push
9releases
7bus factor
493open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 29 authors (cap 12)
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/10 15:14:29 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 322 ⇿
0Stars
322Forks
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.

012525037531062025-112026-042026-09
Major 0Minor 5Patch 3
Direct dependencies 34
RegistryPackageVersion constraintManifest
PyPIopenai==2.44.0pyproject.toml
PyPIanthropic<=0.109.2pyproject.toml
PyPItqdm—pyproject.toml
PyPIpydantic—pyproject.toml
PyPIpydantic_core—pyproject.toml
PyPIdevtools—pyproject.toml
PyPIpackaging>=24.2pyproject.toml
PyPIfastapi—pyproject.toml
PyPImcp>=1.28.1,<2pyproject.toml
PyPIitsdangerous—pyproject.toml
PyPIuvicorn—pyproject.toml
PyPIhttptools—pyproject.toml
PyPIuvloop—pyproject.toml
PyPIhydra-core—pyproject.toml
PyPIomegaconf—pyproject.toml
PyPIrich—pyproject.toml
PyPImlflow-skinny>=3.16.0pyproject.toml
PyPImlflow>=3.16.0pyproject.toml
PyPIscipy>=1.14.1pyproject.toml
PyPIaiohttp>=3.14.1pyproject.toml
PyPIyappi>=1.7.6pyproject.toml
PyPIray>=2.56.1pyproject.toml
PyPIpsutil—pyproject.toml
PyPIdatasets—pyproject.toml
PyPIorjson—pyproject.toml
PyPIurllib3>=2.7.0pyproject.toml
PyPIsqlparse>=0.6.0pyproject.toml
PyPIfonttools>=4.60.2pyproject.toml
PyPIpython-multipart>=0.0.22pyproject.toml
PyPIpyarrow>=23.0.1pyproject.toml
PyPIwandb—pyproject.toml
PyPIGitPython>=3.1.61pyproject.toml
PyPIpyasn1>=0.6.4pyproject.toml
PyPIpydot—pyproject.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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.