Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-22 09:33 UTC

tokio-rs / turmoil

Add hardship to your tests

RustMIT★ 1,262 stars⑂ 75 forkssince Aug 2022View on GitHub ↗

tokio-rs/turmoil holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (78/100) and lowest on Security (42/100). It was last updated 62 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

TokioOrganization
3,108 followers48 public repossince Jul 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioturmoil0.7.2179,19926150 days agodeterministicsimulationtestingnetwork-programmingasynchronous
crates.ioturmoil-net0.1.0201140 days agodeterministicsimulationtestingnetwork-programmingasynchronous

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
18/36Push recency — last push 62 days ago
14.5/36Commit cadence — 21/52 weeks with commits
15.3/18Commit volume — 50 commits in the last year
1/10OpenSSF Scorecard: Maintained — 1 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year50
human_commit_share1
days_since_last_push62
active_weeks_last_year21
How it's scored
27/27Ships releases — 24 releases published
27/36Release recency — latest release 150 days ago
19.8/27Release cadence — a release every ~100 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count24
latest_release_tagv0.7.2
releases_from_tagsno
days_since_latest_release150
mean_days_between_releases100
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?

76Good · 17% of overall
How it's scored
50.3/60Stars — 1,262 stars
15.6/25Forks — 75 forks
6.8/15Watchers — 18 watchers
Inputs used
forks75
stars1,262
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
70/80Monthly downloads — 179,219 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesturmoil, turmoil-net
dependents—
ecosystemscrates
total_downloads16,040,291
monthly_downloads179,219
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.7/22.5Commit distribution — top contributor authored 44% of commits
13.5/13.5Contributor breadth — 36 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled36
top_contributor_share0.437
How it's scored
38.6/42Issue resolution — 92% of issues closed
25.1/30PR acceptance — 186/222 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 10/29 approved changesets -- score normalized to 3
Inputs used
merged_prs186
open_issues5
closed_issues56
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.918
closed_unmerged_prs36
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
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 3,108 followers of tokio-rs
24.3/25Track record — 48 public repos, account ~10 yr old
Inputs used
followers3,108
owner_typeOrganization
is_verifiedno
owner_logintokio-rs
public_repos48
account_age_days3,734

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on crates
35/35Publish recency — latest publish 140 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesturmoil, turmoil-net
ecosystemscrates
any_deprecatedno
min_days_since_publish140

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — crates/turmoil-fs/Cargo.toml ([lints]), crates/turmoil-io-uring/Cargo.toml ([lints]), crates/turmoil-net/Cargo.toml ([lints]), crates/turmoil/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/turmoil
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/turmoil
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 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.5/2.5CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 10/29 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 16 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.5/2.5License — license file detected
0.8/7.5Maintained — 1 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
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
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

78Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md, crates/turmoil-net/CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 90 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.9
agent_instruction_filesCLAUDE.md, crates/turmoil-net/CLAUDE.md
agent_instruction_max_bytes2,620
How it's scored
12.6/18One-command bootstrap — Cargo.toml, crates/turmoil-fs/Cargo.toml, crates/turmoil-io-uring/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — crates/turmoil-fs/Cargo.toml ([lints]), crates/turmoil-io-uring/Cargo.toml ([lints]), crates/turmoil-net/Cargo.toml ([lints]), crates/turmoil/Cargo.toml ([lints])
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, crates/turmoil-fs/Cargo.toml, crates/turmoil-io-uring/Cargo.toml, crates/turmoil-net/Cargo.toml, crates/turmoil/Cargo.toml, examples/axum/Cargo.toml, examples/cluster/Cargo.toml, examples/grpc/Cargo.toml, examples/udp_vpv4_broadcast/Cargo.toml, examples/udp_vpv4_multicast/Cargo.toml, examples/udp_vpv6_multicast/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.4/55Manageable file sizes — 1/98 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes91,081
source_files_sampled98
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — examples/grpc/helloworld.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesexamples/grpc/helloworld.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

1,262GitHub stars
36contributors
50commits, last 12 months
62days since last push
24releases
2bus factor
5open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'turmoil-fs' from its registry
  • Could not fetch crates package 'turmoil-io-uring' from its registry
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 75 ⇿
0Stars
75Forks
24Releases

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.

01325385063757532022-082024-082026-09
Major 0Minor 6Patch 18

Each point covers 4 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-22 09:33 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
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/29 approved changesets -- score normalized to 3
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained1 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 24
RegistryPackageVersion constraintManifest
crates.iobytes1.4crates/turmoil-fs/Cargo.toml
crates.ioindexmap2crates/turmoil-fs/Cargo.toml
crates.iorand0.9crates/turmoil-fs/Cargo.toml
crates.iorand_distr0.5crates/turmoil-fs/Cargo.toml
crates.iotokio1.25.0crates/turmoil-fs/Cargo.toml
crates.iotracing0.1crates/turmoil-fs/Cargo.toml
crates.ioindexmap2crates/turmoil-io-uring/Cargo.toml
crates.iorand0.9crates/turmoil-io-uring/Cargo.toml
crates.iotokio1.25.0crates/turmoil-io-uring/Cargo.toml
crates.ioturmoil-fs0.1.0crates/turmoil-io-uring/Cargo.toml
crates.iobytes1crates/turmoil-net/Cargo.toml
crates.ioindexmap2crates/turmoil-net/Cargo.toml
crates.iotokio1crates/turmoil-net/Cargo.toml
crates.iobytes1.4crates/turmoil/Cargo.toml
crates.ioindexmap2crates/turmoil/Cargo.toml
crates.iorand0.9crates/turmoil/Cargo.toml
crates.iorand_distr0.5crates/turmoil/Cargo.toml
crates.ioregex1crates/turmoil/Cargo.toml
crates.ioscoped-tls1.0.1crates/turmoil/Cargo.toml
crates.iotokio1.25.0crates/turmoil/Cargo.toml
crates.iotracing0.1crates/turmoil/Cargo.toml
crates.ioturmoil-fs0.1.0crates/turmoil/Cargo.toml
crates.ioturmoil-io-uring0.1.0crates/turmoil/Cargo.toml
crates.iouuid1crates/turmoil/Cargo.toml
All dependencies 29

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

RegistryPackageVersionRelation
crates.iobytes—direct
crates.ioindexmap—direct
crates.iorand—direct
crates.iorand_distr—direct
crates.ioregex—direct
crates.ioscoped-tls—direct
crates.iotokio—direct
crates.iotracing—direct
crates.ioturmoil-fs—direct
crates.ioturmoil-io-uring—direct
crates.iouuid—direct
crates.ioasync-stream—indirect
crates.ioaxum—indirect
crates.iogetrandom—indirect
crates.iohttp-body-util—indirect
crates.iohyper—indirect
crates.iohyper-util—indirect
crates.ioio-uring—indirect
crates.iopin-project-lite—indirect
crates.ioprost—indirect
crates.ioprotox—indirect
crates.iotempfile—indirect
crates.iotest-case—indirect
crates.iotokio-test—indirect
crates.iotonic—indirect
crates.iotonic-prost—indirect
crates.iotonic-prost-build—indirect
crates.iotower—indirect
crates.iotracing-subscriber—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — crates.io.