Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 15:31 UTC

treeverse / dvc

🦉 Data Versioning and ML Experiments

PythonApache-2.0★ 15,876 stars⑂ 1,327 forkssince Mar 2017View on GitHub ↗
KindPluginCommand-line toolLibraryhow this is determined

treeverse/dvc holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (96/100) and lowest on Security (45/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

34
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 77 is calibrated to 91 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

121 followers95 public repossince Dec 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIdvc3.67.11,961,110555170 days agoaicollaborationdata-sciencedata-version-controldeveloper-toolsgitmachine-learningreproducibility

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
21.5/36Commit cadence — 31/52 weeks with commits
17.3/18Commit volume — 83 commits in the last year
9/10OpenSSF Scorecard: Maintained — 8 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year83
human_commit_share0.46
days_since_last_push2
active_weeks_last_year31
How it's scored
27/27Ships releases — 100 releases published
27/36Release recency — latest release 170 days ago
27/27Release cadence — a release every ~25.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag3.67.1
releases_from_tagsno
days_since_latest_release170
mean_days_between_releases25.7
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?

96Exceptional · 17% of overall
How it's scored
60/60Stars — 15,876 stars
25/25Forks — 1,327 forks
11.8/15Watchers — 135 watchers
Inputs used
forks1,327
stars15,876
watchers135
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,961,110 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdvc
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,961,110
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.4/22.5Commit distribution — top contributor authored 45% of commits
13.5/13.5Contributor breadth — 97 contributors
10/10OpenSSF Scorecard: Contributors — project has 45 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled97
top_contributor_share0.449
How it's scored
40.4/42Issue resolution — 96% of issues closed
26.2/30PR acceptance — 5,046/5,786 decided PRs merged
0/13Newcomer PR acceptance — 0/2 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 6/11 approved changesets -- score normalized to 5
Inputs used
merged_prs5,046
open_issues180
closed_issues4,713
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d2
issue_closed_ratio0.963
closed_unmerged_prs740
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
15/25Owner reach — 121 followers of treeverse
25/25Track record — 95 public repos, account ~6 yr old
Inputs used
followers121
owner_typeOrganization
is_verifiedno
owner_logintreeverse
public_repos95
account_age_days2,468

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://dvc.org
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsdata-science, machine-learning, reproducibility, data-version-control, developer-tools, ai, unstructured-data
has_wikiyes
homepagehttps://dvc.org
docs_sitehttps://dvc.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no data
3.8/7.5Code-Review — Found 6/11 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 45 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6.8/7.5Maintained — 8 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 9
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.6
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier50
security_posture_before_jurisdiction66
Excluded from scoring (no data or not applicable): CII-Best-Practices, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
19/25Indirect dependencies free of known advisories — 1 affected: diskcache 5.6.3 (moderate)
37.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 217 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages97
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Matched the pypi:dvc@3.67.1 runtime dependency closure — what installing the published package pulls in — 97 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://dvc.org/llms.txt)
40/40Legible commit history — 41 of 46 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://dvc.org/llms.txt
legible_history_share0.891
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 25 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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.25
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/554 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes48,801
source_files_sampled554
oversized_source_files0

Key facts

15,876GitHub stars
97contributors
83commits, last 12 months
2days since last push
100releases
2bus factor
180open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 1,327 ⇿
0Stars
1,327Forks
100Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

2004006008001,0001,2001,4001,327102020-012023-052026-09
Major 0Minor 54Patch 46

Each point covers 7 days.

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-17 15:31 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-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
n/aCII-Best-Practicesinternal error: error during http.Do: Get "https://www.bestpractices.dev/projects.json?url=https://github.com/treeverse/dvc": Get "https://www.bestpractices.dev/projects.json?url=https://github.com/treeverse/dvc": dial tcp 146.75.117.55:443: i/o timeout
5Code-ReviewFound 6/11 approved changesets -- score normalized to 5
10Contributorsproject has 45 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained8 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 9
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 42
RegistryPackageVersion constraintManifest
PyPIattrs>=22.2.0pyproject.toml
PyPIcelery—pyproject.toml
PyPIcolorama>=0.3.9pyproject.toml
PyPIconfigobj>=5.0.9pyproject.toml
PyPIdistro>=1.3pyproject.toml
PyPIdpath<3,>=2.1.0pyproject.toml
PyPIdulwich—pyproject.toml
PyPIdvc-data>=3.18.2,<3.19.0pyproject.toml
PyPIdvc-http>=2.29.0pyproject.toml
PyPIdvc-objects—pyproject.toml
PyPIdvc-render>=1.0.1,<2pyproject.toml
PyPIdvc-studio-client>=0.21,<1pyproject.toml
PyPIdvc-task>=0.3.0,<1pyproject.toml
PyPIflatten-dict<1,>=0.4.1pyproject.toml
PyPIflufl.lock>=8.1.0,<10pyproject.toml
PyPIfsspec>=2024.2.0pyproject.toml
PyPIfuncy>=1.14pyproject.toml
PyPIgrandalf<1,>=0.7pyproject.toml
PyPIgto>=1.6.0,<2pyproject.toml
PyPIhydra-core>=1.1pyproject.toml
PyPIiterative-telemetry>=0.0.7pyproject.toml
PyPIkombu—pyproject.toml
PyPInetworkx>=2.5pyproject.toml
PyPIomegaconf—pyproject.toml
PyPIpackaging>=19pyproject.toml
PyPIpathspec>=0.10.3,<2pyproject.toml
PyPIplatformdirs<5,>=3.1.1pyproject.toml
PyPIpsutil>=5.8pyproject.toml
PyPIpydot>=1.2.4pyproject.toml
PyPIpygtrie>=2.3.2pyproject.toml
PyPIpyparsing>=3.0.0pyproject.toml
PyPIrequests>=2.22pyproject.toml
PyPIrich>=12pyproject.toml
PyPIruamel.yaml>=0.17.11pyproject.toml
PyPIscmrepo>=3.5.2,<4pyproject.toml
PyPIshortuuid>=0.5pyproject.toml
PyPIshtab<2,>=1.3.4pyproject.toml
PyPItabulate>=0.8.7pyproject.toml
PyPItomlkit>=0.11.1pyproject.toml
PyPItqdm<5,>=4.63.1pyproject.toml
PyPIvoluptuous>=0.11.7pyproject.toml
PyPIzc.lockfile>=1.2.1pyproject.toml
All dependencies 42

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

RegistryPackageVersionRelation
PyPIattrs—direct
PyPIcelery—direct
PyPIcolorama—direct
PyPIconfigobj—direct
PyPIdistro—direct
PyPIdpath—direct
PyPIdulwich—direct
PyPIdvc-data—direct
PyPIdvc-http—direct
PyPIdvc-objects—direct
PyPIdvc-render—direct
PyPIdvc-studio-client—direct
PyPIdvc-task—direct
PyPIflatten-dict—direct
PyPIflufl-lock—direct
PyPIfsspec—direct
PyPIfuncy—direct
PyPIgrandalf—direct
PyPIgto—direct
PyPIhydra-core—direct
PyPIiterative-telemetry—direct
PyPIkombu—direct
PyPInetworkx—direct
PyPIomegaconf—direct
PyPIpackaging—direct
PyPIpathspec—direct
PyPIplatformdirs—direct
PyPIpsutil—direct
PyPIpydot—direct
PyPIpygtrie—direct
PyPIpyparsing—direct
PyPIrequests—direct
PyPIrich—direct
PyPIruamel-yaml—direct
PyPIscmrepo—direct
PyPIshortuuid—direct
PyPIshtab—direct
PyPItabulate—direct
PyPItomlkit—direct
PyPItqdm—direct
PyPIvoluptuous—direct
PyPIzc-lockfile—direct
Dependency advisories 1

Installing pypi:dvc@3.67.1 pulls in 97 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
diskcache5.6.3indirectmoderate2—

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.