Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 15:10 UTC

tox-dev / tox-uv

Use https://github.com/astral-sh/uv with tox

PythonMIT★ 351 stars⑂ 37 forkssince Feb 2024View on GitHub ↗
KindLibraryPluginhow this is determined

tox-dev/tox-uv holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on AI Readiness (59/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

92
overall / 100
Excellent

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.

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

Ownership

142 followers49 public repossince Jul 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPItox-uv-bare1.36.04,750,5811237 days agoenvironmentsisolatedtestingvirtual
PyPItox-uv1.36.06,605,7367337 days agoenvironmentsisolatedtestingvirtual

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
32.5/36Commit cadence47/52 weeks with commits
18/18Commit volume114 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_year114
human_commit_share0.38
days_since_last_push2
active_weeks_last_year47

Release discipline

100Exceptional
How it's scored
27/27Ships releases73 releases published
36/36Release recencylatest release 37 days ago
27/27Release cadencea release every ~16.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count73
latest_release_tag1.36.0
releases_from_tagsno
days_since_latest_release37
mean_days_between_releases16.2
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?

64Moderate · 17% of overall
How it's scored
41.3/60Stars351 stars
13/25Forks37 forks
0/15Watchers2 watchers
Inputs used
forks37
stars351
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads11,356,317 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestox-uv-bare, tox-uv
dependents
ecosystemspypi
total_downloads
monthly_downloads11,356,317
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?

70Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.6/22.5Commit distributiontop contributor authored 66% of commits
13.5/13.5Contributor breadth24 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled24
top_contributor_share0.662
How it's scored
42/42Issue resolution100% of issues closed
28/30PR acceptance263/282 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/6 approved changesets -- score normalized to 0
Inputs used
merged_prs263
open_issues0
closed_issues75
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs19
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15.5/25Owner reach142 followers of tox-dev
24.4/25Track record49 public repos, account ~10 yr old
Inputs used
followers142
owner_typeOrganization
is_verifiedno
owner_logintox-dev
public_repos49
account_age_days3,702

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on pypi
35/35Publish recencylatest publish 37 days ago
20/20Version history73 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestox-uv-bare, tox-uv
ecosystemspypi
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests29 out of 29 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 sitehttps://github.com/tox-dev/tox-uv#tox-uv
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicstox
has_wikino
homepage
docs_sitehttps://github.com/tox-dev/tox-uv#tox-uv
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

81Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests29 out of 29 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
0/7.5Code-ReviewFound 0/6 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 17 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate 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
5/5Pinned-Dependenciesall dependencies are pinned
4.5/5SASTSAST tool is not run on all commits -- score normalized to 9
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.6
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_packages14
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:tox-uv@1.36.0 runtime dependency closure — what installing the published package pulls in — 14 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.

59Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history32 of 38 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.842
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingsrc/tox_uv/py.typed, tests/demo_pkg_workspace/packages/demo_foo/src/demo_foo/py.typed
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance23 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configssrc/tox_uv/py.typed, tests/demo_pkg_workspace/packages/demo_foo/src/demo_foo/py.typed
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.23
How it's scored
27/45Type-checkable codePython with type-check config (src/tox_uv/py.typed, tests/demo_pkg_workspace/packages/demo_foo/src/demo_foo/py.typed)
55/55Manageable file sizes0/28 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes36,924
source_files_sampled28
oversized_source_files0

Key facts

351GitHub stars
24contributors
114commits, last 12 months
2days since last push
73releases
1bus factor
0open 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 ★ / 37 ⇿
0Stars
37Forks
67Releases

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.

01325383722024-022025-032026-04
Major 0Minor 34Patch 33

Each point covers 2 days.

OpenSSF Scorecard 7.6 / 10
7.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-08-27 15:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/6 approved changesets -- score normalized to 0
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool is not run on all commits -- score normalized to 9
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPItox-uv-baremeta/pyproject.toml
PyPIuv<1,>=0.9.27meta/pyproject.toml
PyPIpackaging>=26pyproject.toml
PyPItomli>=2.4pyproject.toml
PyPItox<5,>=4.52.1pyproject.toml
PyPItyping-extensions>=4.15pyproject.toml
All dependencies 18

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

RegistryPackageVersionRelation
PyPIpackagingdirect
PyPItoxdirect
PyPItyping-extensionsdirect
PyPIuvdirect
PyPIcheck-wheel-contentsindirect
PyPIcovdefaultsindirect
PyPIdemo-fooindirect
PyPIdemo-rootindirect
PyPIdevpi-processindirect
PyPIdiff-coverindirect
PyPIhatch-vcsindirect
PyPIhatchlingindirect
PyPIpre-commit-uvindirect
PyPIpytestindirect
PyPIpytest-covindirect
PyPIpytest-mockindirect
PyPItwineindirect
PyPItyindirect
Dependency advisories 0

Installing pypi:tox-uv@1.36.0 pulls in 14 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.