Public record
Software health reportschema 0.30.0 · metrics 2.5.0 · 2026-08-03 04:04 UTC

tower-rs / tower-http

HTTP specific Tower utilities.

RustNo license detected★ 902 stars⑂ 225 forkssince Jan 2018View on GitHub ↗
KindLibraryhow this is determined

tower-rs/tower-http holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (89/100) and lowest on Engineering Quality (42/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

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

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

Ownership

TowerOrganization
224 followers7 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
crates.iotower-http0.7.038,905,1303848 days agoasyncfutureshttpioservicenetwork-programmingweb-programmingasynchronous

Metrics by category

Vitality

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

89Excellent · 21% of overall

Development activity

82Excellent
How it's scored
36/36Push recency — last push 1 days ago
18/36Commit cadence — 26/52 weeks with commits
18/18Commit volume — 99 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year99
human_commit_share0.95
days_since_last_push1
active_weeks_last_year26

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 35 releases published
36/36Release recency — latest release 48 days ago
27/27Release cadence — a release every ~44.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count35
latest_release_tagtower-http-0.7.0
releases_from_tagsno
days_since_latest_release48
mean_days_between_releases44.9
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?

73Good · 17% of overall

Popularity & adoption

75Good
How it's scored
47.9/60Stars — 902 stars
19.6/25Forks — 225 forks
7.1/15Watchers — 20 watchers
Inputs used
forks225
stars902
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

52Moderate
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Ecosystem adoption (downloads)

100Exceptional
How it's scored
80/80Monthly downloads — 38,905,130 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestower-http
dependents—
ecosystemscrates
total_downloads374,244,204
monthly_downloads38,905,130
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?

82Excellent · 23% of overall

Maintainer resilience (bus factor)

76Good
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.5/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 23 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.267

Issue & PR responsiveness

90Excellent
How it's scored
36.4/42Issue resolution — 87% of issues closed
26/30PR acceptance — 389/449 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs389
open_issues30
closed_issues194
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.866
closed_unmerged_prs60
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1

Ownership & stewardship

66Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.9/25Owner reach — 224 followers of tower-rs
18.6/25Track record — 7 public repos, account ~9 yr old
Inputs used
followers224
owner_typeOrganization
is_verified—
owner_logintower-rs
public_repos7
account_age_days3,435

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 48 days ago
20/20Version history — 38 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestower-http
ecosystemscrates
any_deprecatedno
min_days_since_publish48

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall

Engineering practices

44Weak
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

40Weak
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

71Good · 16% of overall

Security posture

71Good
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 — 30 out of 30 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 23 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
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 16 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_aggregate7.1
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.

52Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 89 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.937
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

32At Risk
How it's scored
12.6/18One-command bootstrap — Cargo.toml, examples/axum-key-value-store/Cargo.toml, examples/tonic-key-value-store/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 5 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_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, examples/axum-key-value-store/Cargo.toml, examples/tonic-key-value-store/Cargo.toml, examples/warp-key-value-store/Cargo.toml, tower-http/Cargo.toml
dependency_bot_commit_share0.05

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/119 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes59,626
source_files_sampled119
oversized_source_files0

Machine-readable interfaces

80Excellent
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — examples/tonic-key-value-store/proto/key_value_store.proto
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesexamples/tonic-key-value-store/proto/key_value_store.proto

Key facts

902GitHub stars
99contributors
99commits, last 12 months
1days since last push
35releases
3bus factor
30open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 225 ⇿
0Stars
225Forks
35Releases

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.

0408012016020024021652018-042022-052026-07
Major 0Minor 0Patch 0

Each point covers 8 days.

OpenSSF Scorecard 7.1 / 10
7.1aggregate

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-08-03 04: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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 23 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 16 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 23
RegistryPackageVersion constraintManifest
crates.iobitflags2.0.2tower-http/Cargo.toml
crates.iobytes1tower-http/Cargo.toml
crates.iohttp1.0tower-http/Cargo.toml
crates.iopin-project-lite0.2.7tower-http/Cargo.toml
crates.iotower-layer0.3.3tower-http/Cargo.toml
crates.iotower-service0.3tower-http/Cargo.toml
crates.ioasync-compression0.4tower-http/Cargo.toml
crates.iobase640.22tower-http/Cargo.toml
crates.iofutures-core0.3tower-http/Cargo.toml
crates.iofutures-util0.3.14tower-http/Cargo.toml
crates.iohttp-body1.0.0tower-http/Cargo.toml
crates.iohttp-body-util0.1.0tower-http/Cargo.toml
crates.iohttp-range-header0.4.0tower-http/Cargo.toml
crates.iomime0.3.17tower-http/Cargo.toml
crates.iomime_guess2tower-http/Cargo.toml
crates.iopercent-encoding2.1.0tower-http/Cargo.toml
crates.iourl2.5tower-http/Cargo.toml
crates.iotokio1.6tower-http/Cargo.toml
crates.iotokio-util0.7tower-http/Cargo.toml
crates.iotower0.5tower-http/Cargo.toml
crates.iotracing0.1tower-http/Cargo.toml
crates.iohttpdate1.0tower-http/Cargo.toml
crates.iouuid1.0tower-http/Cargo.toml
All dependencies 42

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

RegistryPackageVersionRelation
crates.ioasync-compression—direct
crates.iobase64—direct
crates.iobitflags—direct
crates.iobytes—direct
crates.iofutures-core—direct
crates.iofutures-util—direct
crates.iohttp—direct
crates.iohttp-body—direct
crates.iohttp-body-util—direct
crates.iohttp-range-header—direct
crates.iohttpdate—direct
crates.iomime—direct
crates.iomime_guess—direct
crates.iopercent-encoding—direct
crates.iopin-project-lite—direct
crates.iotokio—direct
crates.iotokio-util—direct
crates.iotower—direct
crates.iotower-layer—direct
crates.iotower-service—direct
crates.iotracing—direct
crates.iourl—direct
crates.iouuid—direct
crates.ioaxum—indirect
crates.iobrotli—indirect
crates.ioclap—indirect
crates.ioflate2—indirect
crates.iohyper—indirect
crates.iohyper-util—indirect
crates.ioonce_cell—indirect
crates.ioprost—indirect
crates.ioprotox—indirect
crates.ioreqwest—indirect
crates.ioserde_json—indirect
crates.iosync_wrapper—indirect
crates.iotokio-stream—indirect
crates.iotonic—indirect
crates.iotonic-prost—indirect
crates.iotonic-prost-build—indirect
crates.iotracing-subscriber—indirect
crates.iowarp—indirect
crates.iozstd—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

Related records

Inspected repositories sharing catalogue tags or ecosystems with tower-rs/tower-http. Read them side by side →

94microsoft/oxidizerOxidizer is a platform for Rust service development which bridges the gaps in the crate ecosystem to deliver a turn-key solution to enable the efficient creation of high-scale high-availability and high-performance services in Rust.Exceptional93actix/actix-netA collection of lower-level libraries for composable network services.Exceptional98tokio-rs/tokioA runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...Exceptional96actix/actix-webActix Web is a powerful, pragmatic, and extremely fast web framework for Rust.Exceptional88cloudwego/voloRust RPC framework with high-performance and strong-extensibility for building micro-services.Excellent87hyperium/h2HTTP 2.0 client & server implementation for Rust.Excellent

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.5.0, schema v0.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io.