Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-15 21:55 UTC

frictionlessdata / frictionless-py

Data management framework for Python that provides functionality to describe, extract, validate, and transform tabular data

Python · HTMLMIT★ 845 stars⑂ 184 forkssince Dec 2014View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

frictionlessdata/frictionless-py holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (89/100) and lowest on AI Readiness (56/100). It was last updated today. A single contributor accounts for most of its recent work.

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

91
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).

Ownership

Frictionless DataOrganization · verified domain
211 followers130 public repossince Nov 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIfrictionless5.21.0602,9943110 days agodata-packagedata-validationfrictionless-datajson-schemajson-table-schemaopen-datatabular-data-package
npmnamepoints to another repo — not scored0.0.21,19025203 days agoprivatenamees6harmonyshimpolyfill

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
8.3/36Commit cadence — 12/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
10/10OpenSSF Scorecard: Maintained — 22 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year30
human_commit_share0.98
days_since_last_push0
active_weeks_last_year12
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~99.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv5.21.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases99.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?

89Excellent · 17% of overall
How it's scored
47.5/60Stars — 845 stars
18.9/25Forks — 184 forks
7.8/15Watchers — 26 watchers
Inputs used
forks184
stars845
watchers26
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
77.1/80Monthly downloads — 602,994 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfrictionless
dependents—
ecosystemspypi
total_downloads—
monthly_downloads602,994
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
9/54Bus factor — 1 contributor(s) cover half of all commits
6.8/22.5Commit distribution — top contributor authored 70% of commits
13.5/13.5Contributor breadth — 85 contributors
10/10OpenSSF Scorecard: Contributors — project has 37 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled85
top_contributor_share0.699
How it's scored
33.1/42Issue resolution — 79% of issues closed
26.7/30PR acceptance — 646/726 decided PRs merged
13/13Newcomer PR acceptance — 4/4 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs646
open_issues230
closed_issues853
prs_merged_7d3
prs_decided_7d3
prs_merged_30d7
prs_decided_30d7
issue_closed_ratio0.788
closed_unmerged_prs80
first_time_authors_30d3
first_time_prs_merged_30d4
first_time_prs_decided_30d4
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
16.7/25Owner reach — 211 followers of frictionlessdata
25/25Track record — 130 public repos, account ~12 yr old
Inputs used
followers211
owner_typeOrganization
is_verifiedyes
owner_loginfrictionlessdata
public_repos130
account_age_days4,721

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://framework.frictionlessdata.io
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://framework.frictionlessdata.io
docs_sitehttps://framework.frictionlessdata.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 24 out of 25 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
1.5/7.5Code-Review — Found 8/30 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 37 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
7.5/7.5Maintained — 22 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
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
Excluded from scoring (no data or not applicable): Branch-Protection, 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
advisories0
affected_packages0
assessed_packages1
unassessed_packages48
affected_by_severitynone
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 1 resolved dependencies against OSV. 48 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.9/40Legible commit history — 66 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.673
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])
11/11Static type checking — frictionless/py.typed
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 2 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_configsfrictionless/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
27/45Type-checkable code — Python with type-check config (frictionless/py.typed)
55/55Manageable file sizes — 0/636 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes46,298
source_files_sampled636
oversized_source_files0

Key facts

845GitHub stars
85contributors
30commits, last 12 months
0days since last push
100releases
1bus factor
230open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'name' points at a different repository (https://github.com/Gozala/name); excluded from ecosystem scoring
  • deps.dev does not index pypi:frictionless@5.21.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 184 ⇿
0Stars
184Forks
98Releases

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.

0408012016020018152015-052021-012026-10
Major 0Minor 15Patch 62

Each point covers 11 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-10-15 21:54 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9CI-Tests24 out of 25 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
10Contributorsproject has 37 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained22 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
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 21
RegistryPackageVersion constraintManifest
PyPIpetl>=1.6pyproject.toml
PyPImarko>=1.0pyproject.toml
PyPIattrs>=22.2.0pyproject.toml
PyPIjinja2>=3.0pyproject.toml
PyPIpyyaml>=5.3pyproject.toml
PyPIisodate>=0.6pyproject.toml
PyPIrfc3986>=1.4pyproject.toml
PyPIchardet>=3.0pyproject.toml
PyPIchardet>=6.0pyproject.toml
PyPIpydantic>=2.0pyproject.toml
PyPIrequests>=2.10pyproject.toml
PyPIhumanize>=4.2pyproject.toml
PyPItabulate>=0.8.10pyproject.toml
PyPIjsonschema>=4.20pyproject.toml
PyPIreferencing>=0.28.4pyproject.toml
PyPIsimpleeval>=0.9.11pyproject.toml
PyPItyper>=0.12pyproject.toml
PyPIvalidators>=0.18pyproject.toml
PyPIpython-slugify>=1.2pyproject.toml
PyPIpython-dateutil>=2.8pyproject.toml
PyPItyping-extensions>=4.3pyproject.toml
All dependencies 49

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

RegistryPackageVersionRelation
PyPIattrs—direct
PyPIchardet—direct
PyPIhumanize—direct
PyPIisodate—direct
PyPIjinja2—direct
PyPIjsonschema—direct
PyPImarko—direct
PyPIpetl—direct
PyPIpydantic—direct
PyPIpython-dateutil—direct
PyPIpython-slugify—direct
PyPIpyyaml—direct
PyPIreferencing—direct
PyPIrequests—direct
PyPIrfc3986—direct
PyPIsimpleeval—direct
PyPItabulate—direct
PyPItyper—direct
PyPItyping-extensions—direct
PyPIvalidators—direct
PyPIboto3—indirect
PyPIdatasette—indirect
PyPIduckdb—indirect
PyPIduckdb-engine—indirect
PyPIezodf—indirect
PyPIfrictionless-ckan-mapper—indirect
PyPIgoogle-api-python-client—indirect
PyPIijson—indirect
PyPIjsonlines—indirect
PyPIlxml—indirect
PyPIopenpyxl—indirect
PyPIpandas—indirect
PyPIpsycopg—indirect
PyPIpsycopg2—indirect
PyPIpyarrow—indirect
PyPIpygithub—indirect
PyPIpygsheets—indirect
PyPIpymysql—indirect
PyPIpyquery—indirect
PyPIpyright1.1.317indirect
PyPIpyzenodo3—indirect
PyPIruff—indirect
PyPIsavreaderwriter—indirect
PyPIsqlalchemy—indirect
PyPItableschema-to-template—indirect
PyPItatsu—indirect
PyPIvisidata—indirect
PyPIxlrd—indirect
PyPIxlwt—indirect
Dependency advisories 0

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

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, npm.