Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 08:03 UTC

john-kurkowski / tldextract

Accurately separates a URL’s subdomain, domain, and public suffix, using the Public Suffix List (PSL).

PythonBSD-3-Clause★ 2,019 stars⑂ 219 forkssince Feb 2011View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

john-kurkowski/tldextract holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (72/100) and lowest on Sustainability & Governance (64/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

John KurkowskiPersonal account
97 followers31 public repossince Jun 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPItldextract5.3.2-6634 days agotlddomainsubdomainurlparseextracturlparseurlsplitpublicsuffixlistpublicsuffixpublicsuffixlist

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
4.2/36Commit cadence — 6/52 weeks with commits
13.1/18Commit volume — 28 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year28
human_commit_share0.99
days_since_last_push10
active_weeks_last_year6
How it's scored
27/27Ships releases — 12 releases published
36/36Release recency — latest release 34 days ago
19.8/27Release cadence — a release every ~114.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tag5.3.2
releases_from_tagsno
days_since_latest_release34
mean_days_between_releases114.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?

67Good · 17% of overall
How it's scored
53.6/60Stars — 2,019 stars
19.5/25Forks — 219 forks
9/15Watchers — 43 watchers
Inputs used
forks219
stars2,019
watchers43
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.4/22.5Commit distribution — top contributor authored 76% of commits
13.5/13.5Contributor breadth — 46 contributors
10/10OpenSSF Scorecard: Contributors — project has 30 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled46
top_contributor_share0.759
How it's scored
38.7/42Issue resolution — 92% of issues closed
22.3/30PR acceptance — 112/151 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/29 approved changesets -- score normalized to 1
Inputs used
merged_prs112
open_issues17
closed_issues202
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.922
closed_unmerged_prs39
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.3/25Owner reach — 97 followers of john-kurkowski
23/25Track record — 31 public repos, account ~16 yr old
Inputs used
followers97
owner_typeUser
is_verified—
owner_loginjohn-kurkowski
public_repos31
account_age_days5,940
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicspython, tldextract, country-codes, suffix, tld, publicsuffix, publicsuffixlist
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

72Good · 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.5CI-Tests — 8 out of 9 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/29 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 30 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 — 15 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Branch-Protection, 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
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_packages7
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:tldextract@5.3.2 runtime dependency closure — what installing the published package pulls in — 7 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.

70Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
25.9/40Legible commit history — 48 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.485
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes957
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff]), tox.ini
11/11Static type checking — tldextract/py.typed
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 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
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstldextract/py.typed
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
27/45Type-checkable code — Python with type-check config (tldextract/py.typed)
55/55Manageable file sizes — 0/18 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes28,334
source_files_sampled18
oversized_source_files0

Key facts

2,019GitHub stars
46contributors
28commits, last 12 months
10days since last push
12releases
1bus factor
17open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'tldextract' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 219 ⇿
0Stars
219Forks
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.

0408012016020024021852012-012019-042026-08
Major 2Minor 4Patch 6

Each point covers 14 days.

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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 08:03 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
8CI-Tests8 out of 9 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/29 approved changesets -- score normalized to 1
10Contributorsproject has 30 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIidna—pyproject.toml
PyPIrequests>=2.1.0pyproject.toml
PyPIrequests-file>=1.4pyproject.toml
PyPIfilelock>=3.0.8pyproject.toml
All dependencies 67

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

RegistryPackageVersionRelation
PyPIfilelock3.32.2direct
PyPIidna3.18direct
PyPIrequests2.34.2direct
PyPIrequests-file3.0.1direct
PyPIast-serialize0.6.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIbuild1.5.0indirect
PyPIcachetools7.1.7indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcharset-normalizer3.4.9indirect
PyPIcolorama0.4.6indirect
PyPIcryptography50.0.0indirect
PyPIdistlib0.4.3indirect
PyPIdocutils0.23indirect
PyPIexceptiongroup1.3.1indirect
PyPIid1.6.1indirect
PyPIimportlib-metadata9.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.1.2indirect
PyPIjaraco-functools4.6.0indirect
PyPIjeepney0.9.0indirect
PyPIkeyring25.7.0indirect
PyPIlibrt0.13.0indirect
PyPImarkdown-it-py4.2.0indirect
PyPImdurl0.1.2indirect
PyPImore-itertools11.1.0indirect
PyPImypy2.3.0indirect
PyPImypy-extensions1.1.0indirect
PyPInh30.3.6indirect
PyPIpackaging26.2indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.0indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpygments2.20.0indirect
PyPIpyproject-api1.11.0indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-discovery1.5.1indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIpyyaml6.0.3indirect
PyPIreadme-renderer45.0indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIresponses0.26.2indirect
PyPIrfc39862.0.0indirect
PyPIrich15.0.0indirect
PyPIruff0.16.1indirect
PyPIsecretstorage3.5.0indirect
PyPIsybil10.1.0indirect
PyPIsybil9.3.0indirect
PyPIsyrupy5.5.3indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItox4.58.0indirect
PyPItox-uv1.36.0indirect
PyPItox-uv-bare1.36.0indirect
PyPItwine7.0.0indirect
PyPItypes-filelock3.2.7indirect
PyPItypes-requests2.33.0.20260712indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.7.0indirect
PyPIuv0.12.1indirect
PyPIvirtualenv21.7.1indirect
PyPIzipp4.1.0indirect
Dependency advisories 0

Installing pypi:tldextract@5.3.2 pulls in 7 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.