Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 18:41 UTC

Smithay / client-toolkit

Smithay's toolkit for writing wayland clients

RustMIT★ 435 stars⑂ 96 forkssince Apr 2018View on GitHub ↗
KindDesktop applicationLibraryhow this is determined

Smithay/client-toolkit holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on AI Readiness (51/100). It was last updated 29 days ago. 3 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

SmithayOrganization
190 followers19 public repossince Jun 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iosmithay-client-toolkit0.21.14,454,1735335 days agoclientwaylandgui

Metrics by category

Vitality

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

65Good · 21% of overall

Development activity

61Moderate
How it's scored
28.8/36Push recency — last push 29 days ago
9/36Commit cadence — 13/52 weeks with commits
13.6/18Commit volume — 32 commits in the last year
10/10OpenSSF Scorecard: Maintained — 15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year32
human_commit_share1
days_since_last_push29
active_weeks_last_year13

Release discipline

72Good
How it's scored
16.2/27Ships releases — 51 version tags (no GitHub releases)
36/36Release recency — latest release 35 days ago
12.6/27Release cadence — a release every ~134 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count51
latest_release_tagv0.21.1
releases_from_tagsyes
days_since_latest_release35
mean_days_between_releases134
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

Popularity & adoption

65Good
How it's scored
42.8/60Stars — 435 stars
16.5/25Forks — 96 forks
5.3/15Watchers — 10 watchers
Inputs used
forks96
stars435
watchers10
growth_stateorganic
growth_factor_pct100

Community health

70Good
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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

100Exceptional
How it's scored
80/80Monthly downloads — 4,454,173 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessmithay-client-toolkit
dependents—
ecosystemscrates
total_downloads56,418,168
monthly_downloads4,454,173
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?

79Good · 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 26% of commits
13.5/13.5Contributor breadth — 56 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled56
top_contributor_share0.265

Issue & PR responsiveness

78Good
How it's scored
26/42Issue resolution — 62% of issues closed
26.6/30PR acceptance — 335/378 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs335
open_issues54
closed_issues88
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.62
closed_unmerged_prs43
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.

Ownership & stewardship

68Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.4/25Owner reach — 190 followers of Smithay
21.5/25Track record — 19 public repos, account ~9 yr old
Inputs used
followers190
owner_typeOrganization
is_verifiedno
owner_loginSmithay
public_repos19
account_age_days3,374

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall

Engineering practices

50Moderate
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 10 out of 17 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

65Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://smithay.github.io/client-toolkit
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://smithay.github.io/client-toolkit
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall

Security posture

54Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.2/2.5CI-Tests — 10 out of 17 merged PRs checked by a CI test -- score normalized to 5
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 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
7.5/7.5Maintained — 15 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 — 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_aggregate5.4
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.

51Moderate · 4% of overall

Agent context & guidance

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

Verify loop (build / test / typecheck)

35Weak
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
11/11Lint / format config — rustfmt.toml
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_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0

Code legibility for models

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

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

435GitHub stars
56contributors
32commits, last 12 months
29days since last push
51releases
3bus factor
54open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-15: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 435 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 426 ★ / 96 ⇿
426Stars
96Forks
49Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-15. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01002003004005004269572018-042022-062026-07
Major 0Minor 20Patch 29

Each point covers 8 days.

OpenSSF Scorecard 5.4 / 10
5.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-08-27 18:41 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
5CI-Tests10 out of 17 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
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
10Maintained15 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
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 19
RegistryPackageVersion constraintManifest
crates.iobitflags2.4Cargo.toml
crates.iobytemuck1.13.0Cargo.toml
crates.iocursor-icon1.2.0Cargo.toml
crates.iolog0.4Cargo.toml
crates.iomemmap20.9.0Cargo.toml
crates.iorustix1.1.4Cargo.toml
crates.iothiserror2.0.12Cargo.toml
crates.iowayland-client0.31.14Cargo.toml
crates.iowayland-cursor0.31.0Cargo.toml
crates.iowayland-protocols0.32.9Cargo.toml
crates.iowayland-protocols-experimental20251230.0.1Cargo.toml
crates.iowayland-protocols-misc0.3.6Cargo.toml
crates.iowayland-protocols-wlr0.3.1Cargo.toml
crates.iowayland-scanner0.31.0Cargo.toml
crates.iowayland-csd-frame0.3.0Cargo.toml
crates.ioxkbcommon0.8.0Cargo.toml
crates.ioxkeysym0.2.0Cargo.toml
crates.iocalloop0.14.0Cargo.toml
crates.iocalloop-wayland-source0.4.0Cargo.toml
All dependencies 28

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

RegistryPackageVersionRelation
crates.iobitflags—direct
crates.iobytemuck—direct
crates.iocalloop—direct
crates.iocalloop-wayland-source—direct
crates.iocursor-icon—direct
crates.iolog—direct
crates.iomemmap2—direct
crates.iorustix—direct
crates.iothiserror—direct
crates.iowayland-client—direct
crates.iowayland-csd-frame—direct
crates.iowayland-cursor—direct
crates.iowayland-protocols—direct
crates.iowayland-protocols-experimental—direct
crates.iowayland-protocols-misc—direct
crates.iowayland-protocols-wlr—direct
crates.iowayland-scanner—direct
crates.ioxkbcommon—direct
crates.ioxkeysym—direct
crates.iodrm-fourcc—indirect
crates.ioenv_logger—indirect
crates.iofont-kit—indirect
crates.ioimage—indirect
crates.iopkg-config—indirect
crates.iopollster—indirect
crates.ioraqote—indirect
crates.ioraw-window-handle—indirect
crates.iowgpu—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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with Smithay/client-toolkit. Read them side by side →

83Smithay/wayland-rsRust implementation of the wayland protocol (client and server).Excellent94rust-windowing/winitWindow handling library in pure RustExceptional84c410-f3r/wtxWritten by humans. WTX is a collection of different transport implementations and related tools focused primarily on web technologies.Excellent98bevyengine/bevyA refreshingly simple data-driven game engine built in RustExceptional98valkey-io/valkey-glideAn open source Valkey client library that supports Valkey, and Redis open source 6.2, 7.0 and 7.2. Valkey GLIDE is designed for reliability, optimized performance, and high-availability, for Valkey and Redis OSS based applications. GLIDE is a multi language client library, written in Rust with programming language bindings, such as Java and PythonExceptional96slint-ui/slintSlint is an open-source declarative GUI toolkit to build native user interfaces for Rust, C++, JavaScript, or Python apps.Exceptional

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.