Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 01:08 UTC

python-trio / trustme

#1 quality TLS certs while you wait, for the discerning tester

PythonCustom license★ 603 stars⑂ 32 forkssince Jul 2017View on GitHub ↗

python-trio/trustme holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (78/100) and lowest on AI Readiness (45/100). It was last updated 15 days ago. 2 contributors account for most of its recent work.

77
overall / 100
Good

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.

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

Ownership

python-trioOrganization
144 followers32 public repossince Mar 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPItrustme1.2.1-16560 days ago

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 15 days ago
7.6/36Commit cadence11/52 weeks with commits
12.1/18Commit volume21 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year21
human_commit_share
days_since_last_push15
active_weeks_last_year11
How it's scored
27/27Ships releases3 releases published
7.2/36Release recencylatest release 560 days ago
27/27Release cadencea release every ~43.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count3
latest_release_tagv1.2.1
releases_from_tagsno
days_since_latest_release560
mean_days_between_releases43.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

70Good · 17% of overall
How it's scored
45.1/60Stars603 stars
12.4/25Forks32 forks
4.7/15Watchers8 watchers
Inputs used
forks32
stars603
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.2/22.5Commit distributiontop contributor authored 46% of commits
13.5/13.5Contributor breadth24 contributors
10/10OpenSSF Scorecard: Contributorsproject has 49 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled24
top_contributor_share0.457
How it's scored
38.3/42Issue resolution91% of issues closed
25/30PR acceptance569/682 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs569
open_issues3
closed_issues31
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.912
closed_unmerged_prs113
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
15.5/25Owner reach144 followers of python-trio
23.1/25Track record32 public repos, account ~9 yr old
Inputs used
followers144
owner_typeOrganization
is_verified
owner_loginpython-trio
public_repos32
account_age_days3,415
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
14/35Publish recencylatest publish 560 days ago
20/20Version history16 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestrustme
ecosystemspypi
any_deprecatedno
min_days_since_publish560

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests19 out of 22 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://trustme.rtfd.io
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicstls, tls-certificate, testing, testing-tools, python, ssl, ssl-certificate
has_wikino
homepagehttps://trustme.rtfd.io
docs_sitehttps://trustme.rtfd.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests19 out of 22 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 49 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.2/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapdocs/Makefile, noxfile.py
22/22Automated tests
0/11Lint / format config
11/11Static type checkingsrc/trustme/py.typed
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile, noxfile.py
has_devcontainerno
has_linter_configno
typecheck_configssrc/trustme/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (src/trustme/py.typed)
55/55Manageable file sizes0/9 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes19,850
source_files_sampled9
oversized_source_files0

Key facts

603GitHub stars
24contributors
21commits, last 12 months
15days since last push
3releases
2bus factor
3open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 5.5 / 10
5.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-07-17 01:07 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-Tests19 out of 22 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 49 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIcryptography>=3.1pyproject.toml
PyPIidna>=2.0pyproject.toml
All dependencies 59

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

RegistryPackageVersionRelation
PyPIcryptographydirect
PyPIcryptography48.0.0direct
PyPIidnadirect
PyPIidna3.18direct
PyPIalabaster1.0.0indirect
PyPIargcomplete3.7.0indirect
PyPIast-serialize0.6.0indirect
PyPIattrs26.1.0indirect
PyPIbabel2.18.0indirect
PyPIblack26.5.1indirect
PyPIcertifi2026.6.17indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIclick8.4.2indirect
PyPIcolorlog6.10.1indirect
PyPIcoverage7.14.3indirect
PyPIdependency-groups1.3.1indirect
PyPIdistlib0.4.3indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock3.29.4indirect
PyPIhumanize4.16.0indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIisort8.0.1indirect
PyPIjinja23.1.6indirect
PyPIlibrt0.12.0indirect
PyPImarkupsafe3.0.3indirect
PyPImypy2.1.0indirect
PyPImypy-extensions1.1.0indirect
PyPInox2026.4.10indirect
PyPIpackaging26.2indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.10.0indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpygments2.20.0indirect
PyPIpyopenssl26.2.0indirect
PyPIpytest9.1.1indirect
PyPIpython-discovery1.4.2indirect
PyPIpytokens0.4.1indirect
PyPIrequests2.34.2indirect
PyPIservice-identity26.1.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsphinx8.1.3indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIsphinxcontrib-trio1.2.0indirect
PyPItomli2.4.1indirect
PyPItypes-cffi2.0.0.20260518indirect
PyPItypes-pyopenssl24.1.0.20240722indirect
PyPItypes-setuptools82.0.0.20260518indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
PyPIvirtualenv21.5.1indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.