Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 10:53 UTC

google / grain

Library for reading and processing ML training data.

PythonApache-2.0★ 778 stars⑂ 86 forkssince Aug 2022View on GitHub ↗

google/grain holds a health index of 95 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on AI Readiness (43/100). It was last updated 2 days ago. 2 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

GoogleOrganization · verified domain
78,338 followers2,900 public repossince Jan 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIgrain0.2.18797,2402086 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 recency — last push 2 days ago
34.6/36Commit cadence — 50/52 weeks with commits
18/18Commit volume — 238 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year238
human_commit_share1
days_since_last_push2
active_weeks_last_year50
How it's scored
27/27Ships releases — 12 releases published
36/36Release recency — latest release 86 days ago
19.8/27Release cadence — a release every ~45.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tagv0.2.18
releases_from_tagsno
days_since_latest_release86
mean_days_between_releases45.9
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?

82Excellent · 17% of overall
How it's scored
46.9/60Stars — 778 stars
16.1/25Forks — 86 forks
5.8/15Watchers — 12 watchers
Inputs used
forks86
stars778
watchers12
growth_stateorganic
growth_factor_pct100

Community health

85Excellent
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
78.7/80Monthly downloads — 797,240 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgrain
dependents—
ecosystemspypi
total_downloads—
monthly_downloads797,240
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.7/22.5Commit distribution — top contributor authored 44% of commits
13.5/13.5Contributor breadth — 69 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled69
top_contributor_share0.435
How it's scored
22/42Issue resolution — 52% of issues closed
15.5/30PR acceptance — 609/1,181 decided PRs merged
0/13Newcomer PR acceptance — 0/2 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 16/30 approved changesets -- score normalized to 5
Inputs used
merged_prs609
open_issues41
closed_issues45
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d2
issue_closed_ratio0.523
closed_unmerged_prs572
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 78,338 followers of google
25/25Track record — 2,900 public repos, account ~14 yr old
Inputs used
followers78,338
owner_typeOrganization
is_verifiedyes
owner_logingoogle
public_repos2,900
account_age_days5,351

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 14 out of 14 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://google-grain.readthedocs.io
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsdata-pr, jax, machine-learning, python
has_wikino
homepagehttps://google-grain.readthedocs.io
docs_sitehttps://google-grain.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 16/30 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 12 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.3
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories6
affected_packages3
assessed_packages26
unassessed_packages24
affected_by_severityhigh 1, moderate 1, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 26 resolved dependencies against OSV. 24 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8/40Legible commit history — 15 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.15
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
54.6/55Manageable file sizes — 1/137 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes73,461
source_files_sampled137
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — grain/proto/execution_summary.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — notebooks
Inputs used
example_dirsnotebooks
has_mcp_signalno
api_schema_filesgrain/proto/execution_summary.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

778GitHub stars
69contributors
238commits, last 12 months
2days since last push
12releases
2bus factor
41open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-16: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 778 stars today.
  • Could not fetch pypi package 'grain._src.python.experimental.index_shuffle.python.index_shuffle_module' from its registry

More detail

Star and fork history 752 ★ / 86 ⇿
752Stars
86Forks
12Releases

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.

Star history is shown as collected on 2026-07-16. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

020040060080075286212022-082024-082026-08
Major 0Minor 0Patch 12

Each point covers 4 days.

OpenSSF Scorecard 6.3 / 10
6.3aggregate

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-12 10:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 16/30 approved changesets -- score normalized to 5
10Contributorsproject has 12 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 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIabsl-py—pyproject.toml
PyPIarray-record>=0.8.1pyproject.toml
PyPIcloudpickle—pyproject.toml
PyPIetils—pyproject.toml
PyPInumpy—pyproject.toml
PyPIportpicker—pyproject.toml
PyPIprotobuf>=5.28.3pyproject.toml
All dependencies 50

Full resolved dependency set from the GitHub dependency graph: 14 direct and 36 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIabsl-py—direct
PyPIabsl-py2.3.1direct
PyPIarray-record—direct
PyPIarray-record0.7.2direct
PyPIarray-record0.8.2direct
PyPIcloudpickle—direct
PyPIcloudpickle3.1.1direct
PyPIetils—direct
PyPIetils1.12.2direct
PyPInumpy—direct
PyPInumpy2.3.4direct
PyPIportpicker—direct
PyPIportpicker1.6.0direct
PyPIprotobuf—direct
PyPIattrs—indirect
PyPIattrs25.3.0indirect
PyPIfsspec2025.9.0indirect
PyPIgrpcio-tools—indirect
PyPIimportlib-resources6.5.2indirect
PyPIiniconfig2.3.0indirect
PyPIjax—indirect
PyPIjax0.8.0indirect
PyPIjaxlib0.8.0indirect
PyPIml-dtypes0.5.3indirect
PyPImyst-nb—indirect
PyPImyst-parser—indirect
PyPIopt-einsum3.4.0indirect
PyPIpackaging25.0indirect
PyPIparameterized—indirect
PyPIparameterized0.9.0indirect
PyPIpluggy1.6.0indirect
PyPIprometheus-client—indirect
PyPIprometheus-client0.21.1indirect
PyPIpsutil7.2.2indirect
PyPIpyarrow—indirect
PyPIpyarrow22.0.0indirect
PyPIpydata-sphinx-theme—indirect
PyPIpygments2.19.2indirect
PyPIpytest—indirect
PyPIpytest8.4.2indirect
PyPIscipy1.16.2indirect
PyPIsphinx—indirect
PyPIsphinx-autoapi—indirect
PyPIsphinx-autodoc2—indirect
PyPIsphinx-book-theme—indirect
PyPIsphinx-copybutton—indirect
PyPIsphinx-design—indirect
PyPItyping-extensions—indirect
PyPItyping-extensions4.13.2indirect
PyPIzipp3.21.0indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 26 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct. 24 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
pyarrow22.0.0indirecthigh223.0.1
pytest8.4.2indirectmoderate29.0.3
pygments2.19.2indirectlow22.20.0

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 statistics — PyPI.