Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 07:34 UTC

capitalone / datacompy

Pandas, Polars, Spark, and Snowpark DataFrame comparison for humans and more!

PythonApache-2.0★ 658 stars⑂ 167 forkssince Mar 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

capitalone/datacompy holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (95/100) and lowest on Security (70/100). It was last updated 1 day 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

Capital OneOrganization
466 followers52 public repossince Sep 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIdatacompy1.0.43,513,5626951 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
9.7/36Commit cadence — 14/52 weeks with commits
14/18Commit volume — 35 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year35
human_commit_share0.98
days_since_last_push1
active_weeks_last_year14

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 68 releases published
36/36Release recency — latest release 50 days ago
27/27Release cadence — a release every ~15.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count68
latest_release_tagv1.0.4
releases_from_tagsno
days_since_latest_release50
mean_days_between_releases15.5
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?

71Good · 17% of overall
How it's scored
45.7/60Stars — 658 stars
18.5/25Forks — 167 forks
7/15Watchers — 19 watchers
Inputs used
forks167
stars658
watchers19
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 3,513,562 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdatacompy
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,513,562
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?

73Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.6/22.5Commit distribution — top contributor authored 57% of commits
13.5/13.5Contributor breadth — 36 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled36
top_contributor_share0.574
How it's scored
40.5/42Issue resolution — 96% of issues closed
24.6/30PR acceptance — 304/371 decided PRs merged
8.7/13Newcomer PR acceptance — 2/3 first-time contributors' PRs merged in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 25/27 approved changesets -- score normalized to 9
Inputs used
merged_prs304
open_issues7
closed_issues186
prs_merged_7d4
prs_decided_7d4
prs_merged_30d6
prs_decided_30d7
issue_closed_ratio0.964
closed_unmerged_prs67
first_time_authors_30d3
first_time_prs_merged_30d2
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
19.2/25Owner reach — 466 followers of capitalone
24.6/25Track record — 52 public repos, account ~12 yr old
Inputs used
followers466
owner_typeOrganization
is_verifiedno
owner_logincapitalone
public_repos52
account_age_days4,399

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

95Exceptional · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff]), tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 26 out of 28 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://capitalone.github.io/datacompy/
10/10Repository description
10/10Topics — 14 topics
10/10Wiki
Inputs used
topicspython, pandas, spark, data, data-science, compare, dataframes, numpy, pyspark, fugue, dask, polars, snowflake, snowpark
has_wikiyes
homepagehttps://capitalone.github.io/datacompy/
docs_sitehttps://capitalone.github.io/datacompy/
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
1.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 26 out of 28 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 25/27 approved changesets -- score normalized to 9
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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 — 15 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.3
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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages9
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:datacompy@1.0.4 runtime dependency closure — what installing the published package pulls in — 9 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.

76Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 82 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.837
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes14,098
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff]), tox.ini
11/11Static type checking — datacompy/py.typed
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsdatacompy/py.typed
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (datacompy/py.typed)
51.4/55Manageable file sizes — 4/61 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes110,311
source_files_sampled61
oversized_source_files4

Key facts

658GitHub stars
36contributors
35commits, last 12 months
1days since last push
68releases
1bus factor
7open 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 ★ / 167 ⇿
0Stars
167Forks
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.

0408012016020016742018-032022-062026-09
Major 1Minor 13Patch 44

Each point covers 8 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-20 07:33 UTC

10Binary-Artifactsno binaries found in the repo
2Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests26 out of 28 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 25/27 approved changesets -- score normalized to 9
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
PyPIjinja2>=3pyproject.toml
PyPInumpy>=1.26.4,<2.6pyproject.toml
PyPIordered-set>=4.0.2,<=4.1pyproject.toml
PyPIpandas>=2.2,<3.1pyproject.toml
PyPIpolars>=0.20.4,<1.45pyproject.toml
All dependencies 9

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

RegistryPackageVersionRelation
PyPIjinja2—direct
PyPInumpy—direct
PyPIordered-set—direct
PyPIpandas—direct
PyPIpolars—direct
PyPIpyspark—indirect
PyPIruff—indirect
PyPIsetuptools—indirect
PyPIsnowflake-snowpark-python—indirect
Dependency advisories 0

Installing pypi:datacompy@1.0.4 pulls in 9 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 statistics — PyPI.