Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 14:55 UTC

A5rocks / trio

Trio – a friendly Python library for async concurrency and I/O

PythonCustom license★ 0 stars⑂ 0 forkssince Oct 2021forkView on GitHub ↗

A5rocks/trio holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (78/100) and lowest on Community & Adoption (9/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

56
overall / 100
Moderate

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.

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

Ownership

A5rocksPersonal account
56 followers44 public repossince Jun 2018

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
PyPItriopoints to another repo — not scored0.35.041,065,5744515 days agoasyncionetworkingtrio

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 1 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 177 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year177
human_commit_share0.71
days_since_last_push1
active_weeks_last_year49
How it's scored
16.2/27Ships releases — 35 version tags (no GitHub releases)
0/36Release recency — latest release 830 days ago
27/27Release cadence — a release every ~43.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count35
latest_release_tagv0.26.2
releases_from_tagsyes
days_since_latest_release830
mean_days_between_releases43.6
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?

9Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno

Sustainability & Governance

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

46Weak · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
14.9/22.5Commit distribution — top contributor authored 34% of commits
13.5/13.5Contributor breadth — 95 contributors
10/10OpenSSF Scorecard: Contributors — project has 94 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled95
top_contributor_share0.337
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.6/25Owner reach — 56 followers of A5rocks
24/25Track record — 44 public repos, account ~8 yr old
Inputs used
followers56
owner_typeUser
is_verified—
owner_loginA5rocks
public_repos44
account_age_days3,064
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.black]), tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://trio.readthedocs.io
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://trio.readthedocs.io
docs_sitehttps://trio.readthedocs.io
has_readmeno
has_docs_diryes
has_descriptionno

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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 94 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 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 — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 22 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, 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
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
advisories1
affected_packages1
assessed_packages85
unassessed_packages4
affected_by_severityhigh 1
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 85 resolved dependencies against OSV. 4 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29.3/40Legible commit history — 39 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.549
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.black]), tox.ini
11/11Static type checking — src/trio/py.typed
0/10Reproducible environment
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/trio/py.typed
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/trio/py.typed)
54.3/55Manageable file sizes — 2/162 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes129,217
source_files_sampled162
oversized_source_files2

Key facts

0GitHub stars
95contributors
177commits, last 12 months
1days since last push
35releases
3bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • pypi package 'trio' points at a different repository (https://github.com/python-trio/trio); excluded from ecosystem scoring
  • deps.dev does not index pypi:trio@0.35.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-11-16 14: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
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 94 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities22 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIattrs>= 23.2.0pyproject.toml
PyPIsortedcontainers—pyproject.toml
PyPIidna—pyproject.toml
PyPIoutcome—pyproject.toml
PyPIsniffio>= 1.3.0pyproject.toml
PyPIcffi>=1.14pyproject.toml
PyPIexceptiongroup—pyproject.toml
All dependencies 89

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

RegistryPackageVersionRelation
PyPIattrs—direct
PyPIattrs26.1.0direct
PyPIcffi—direct
PyPIcffi2.1.1direct
PyPIexceptiongroup1.3.1direct
PyPIidna3.20direct
PyPIoutcome1.3.0.post0direct
PyPIsniffio—direct
PyPIsniffio1.3.1direct
PyPIsortedcontainers2.4.0direct
PyPIalabaster1.0.0indirect
PyPIast-serialize0.13.1indirect
PyPIastor0.8.1indirect
PyPIastroid4.3.4indirect
PyPIasync-generator1.10indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIblack26.10.1indirect
PyPIcertifi2026.10.23indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.2indirect
PyPIclick8.5.0indirect
PyPIcodespell2.4.3indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.17.0indirect
PyPIcryptography50.0.2indirect
PyPIdill0.4.1indirect
PyPIdistlib0.4.4indirect
PyPIdocutils0.22.4indirect
PyPIdocutils0.23indirect
PyPIfilelock4.2.6indirect
PyPIidentify2.6.20indirect
PyPIimagesize2.0.1indirect
PyPIimmutables0.21indirect
PyPIiniconfig2.3.1indirect
PyPIisort9.0.2indirect
PyPIjedi0.20.1indirect
PyPIjinja23.1.6indirect
PyPIlibrt0.16.0indirect
PyPImarkupsafe3.0.4indirect
PyPImccabe0.7.0indirect
PyPImypy2.4.1indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.12.0indirect
PyPIpackaging26.3indirect
PyPIparso0.8.7indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.14.2indirect
PyPIpluggy1.7.0indirect
PyPIpre-commit4.7.0indirect
PyPIpycparser3.12indirect
PyPIpygments2.21.0indirect
PyPIpylint4.1.3indirect
PyPIpyopenssl26.4.0indirect
PyPIpyright1.1.414indirect
PyPIpytest9.2.0indirect
PyPIpython-discovery1.9.0indirect
PyPIpytokens0.4.1indirect
PyPIpyyaml6.0.3indirect
PyPIrequests2.34.2indirect
PyPIroman-numerals4.1.0indirect
PyPIruff0.17.4indirect
PyPIsetuptools—indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsoupsieve3.0.4indirect
PyPIsphinx9.0.4indirect
PyPIsphinx9.1.1indirect
PyPIsphinx-codeautolink0.19.0indirect
PyPIsphinx-rtd-theme3.1.0indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jquery4.1indirect
PyPIsphinxcontrib-jsmath2.0.0indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIsphinxcontrib-trio1.2.0indirect
PyPItomlkit0.15.2indirect
PyPItowncrier26.9.0indirect
PyPItrustme1.2.1indirect
PyPItypes-cffi2.1.0.20260827indirect
PyPItypes-docutils0.23.0.20261030indirect
PyPItypes-pyopenssl24.1.0.20240722indirect
PyPItypes-pyyaml6.0.12.20261030indirect
PyPItypes-setuptools84.0.0.20261006indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.8.0indirect
PyPIuv0.13.7indirect
PyPIvirtualenv21.15.2indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
soupsieve3.0.4indirecthigh14.0.0

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.