Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 13:03 UTC

python-trio / trio-websocket

WebSocket client and server implementation for Python Trio

PythonMIT★ 81 stars⑂ 33 forkssince Aug 2018View on GitHub ↗

python-trio/trio-websocket holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (72/100) and lowest on Vitality (20/100). It was last updated 269 days ago. 2 contributors account for most of its recent work.

45
overall / 100
Weak

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.

45
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 47 is calibrated to 45 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 publishTags
PyPItrio-websocket0.12.2-22508 days agowebsocketclientservertrio

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 269 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share
days_since_last_push269
active_weeks_last_year1
How it's scored
16.2/27Ships releases21 version tags (no GitHub releases)
7.2/36Release recencylatest release 508 days ago
12.6/27Release cadencea release every ~164.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tag0.12.2
releases_from_tagsyes
days_since_latest_release508
mean_days_between_releases164.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?

58Moderate · 17% of overall
How it's scored
30.9/60Stars81 stars
12.5/25Forks33 forks
4.3/15Watchers7 watchers
Inputs used
forks33
stars81
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.7/22.5Commit distributiontop contributor authored 48% of commits
13.5/13.5Contributor breadth14 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled14
top_contributor_share0.482
How it's scored
34.6/42Issue resolution82% of issues closed
22/30PR acceptance74/101 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs74
open_issues17
closed_issues80
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.825
closed_unmerged_prs27
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,416
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 508 days ago
20/20Version history22 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestrio-websocket
ecosystemspypi
any_deprecatedno
min_days_since_publish508

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests1 out of 6 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

25At Risk · 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
0.2/2.5CI-Tests1 out of 6 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 5/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

52Moderate · 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 bootstrapMakefile, docs/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtrio_websocket/py.typed
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configno
typecheck_configstrio_websocket/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (trio_websocket/py.typed)
50.4/55Manageable file sizes1/12 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes72,543
source_files_sampled12
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

81GitHub stars
14contributors
1commits, last 12 months
269days since last push
21releases
2bus factor
17open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 2.5 / 10
2.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-18 13:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
1CI-Tests1 out of 6 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities20 existing vulnerabilities detected
All dependencies 84

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

RegistryPackageVersionRelation
PyPIalabaster0.7.13indirect
PyPIastroid3.2.4indirect
PyPIastroid3.3.8indirect
PyPIattrs25.1.0indirect
PyPIbabel2.17.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIbuild1.2.2.post1indirect
PyPIcertifi2025.1.31indirect
PyPIcffi1.17.1indirect
PyPIcharset-normalizer3.4.1indirect
PyPIclick8.1.8indirect
PyPIcoverage7.6.1indirect
PyPIcryptography44.0.1indirect
PyPIcryptography46.0.1indirect
PyPIdill0.3.9indirect
PyPIdocutils0.20.1indirect
PyPIexceptiongroupindirect
PyPIexceptiongroup1.2.2indirect
PyPIh110.14.0indirect
PyPIid1.5.0indirect
PyPIidna3.10indirect
PyPIimagesize1.4.1indirect
PyPIimportlib-metadata8.5.0indirect
PyPIimportlib-resources6.4.5indirect
PyPIiniconfig2.0.0indirect
PyPIisort5.13.2indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.0.1indirect
PyPIjaraco-functools4.1.0indirect
PyPIjinja23.1.5indirect
PyPIkeyring25.5.0indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkupsafe2.1.5indirect
PyPImccabe0.7.0indirect
PyPImdurl0.1.2indirect
PyPImore-itertools10.5.0indirect
PyPImypy1.14.1indirect
PyPImypy-extensions1.0.0indirect
PyPInh30.2.20indirect
PyPIoutcomeindirect
PyPIoutcome1.3.0.post0indirect
PyPIpackaging24.2indirect
PyPIpip-tools7.4.1indirect
PyPIplatformdirs4.3.6indirect
PyPIpluggy1.5.0indirect
PyPIpycparser2.22indirect
PyPIpygments2.19.1indirect
PyPIpylint3.2.7indirect
PyPIpylint3.3.4indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest8.3.4indirect
PyPIpytest-cov5.0.0indirect
PyPIpytest-trio0.8.0indirect
PyPIpytz2025.1indirect
PyPIreadme-renderer43.0indirect
PyPIrequests2.32.3indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrfc39862.0.0indirect
PyPIrich13.9.4indirect
PyPIsniffio1.3.1indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsortedcontainers2.4.0indirect
PyPIsphinx7.1.2indirect
PyPIsphinx-rtd-theme3.0.2indirect
PyPIsphinxcontrib-applehelp1.0.4indirect
PyPIsphinxcontrib-devhelp1.0.2indirect
PyPIsphinxcontrib-htmlhelp2.0.1indirect
PyPIsphinxcontrib-jquery4.1indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.3indirect
PyPIsphinxcontrib-serializinghtml1.1.5indirect
PyPIsphinxcontrib-trio1.1.2indirect
PyPItomli2.2.1indirect
PyPItomlkit0.13.2indirect
PyPItrioindirect
PyPItrio0.27.0indirect
PyPItrustme1.1.0indirect
PyPItwine6.1.0indirect
PyPItyping-extensions4.12.2indirect
PyPIurllib32.2.3indirect
PyPIwheel0.45.1indirect
PyPIwsprotoindirect
PyPIwsproto1.2.0indirect
PyPIzipp3.20.2indirect
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.12.0 — full methodology · metrics wiki.

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