Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 02:13 UTC

restatedev / sdk-rust

Rust SDK for restate.dev

RustMIT★ 83 stars⑂ 25 forkssince Aug 2024View on GitHub ↗

restatedev/sdk-rust holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (80/100) and lowest on Community & Adoption (56/100). It was last updated today. A single contributor accounts 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

RestateOrganization
327 followers82 public repossince Jan 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iorestate-sdk0.11.084,610150 days ago
crates.iorestate-sdk-macros0.11.084,638140 days ago
crates.iorestate-sdk-testcontainers0.11.032,37870 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.8/36Commit cadence17/52 weeks with commits
14.6/18Commit volume41 commits in the last year
10/10OpenSSF Scorecard: Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year41
human_commit_share1
days_since_last_push0
active_weeks_last_year17
How it's scored
27/27Ships releases11 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~75.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tagv0.11.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases75.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?

56Moderate · 17% of overall
How it's scored
31/60Stars83 stars
11.5/25Forks25 forks
0/15Watchers2 watchers
Inputs used
forks25
stars83
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
70.7/80Monthly downloads201,626 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesrestate-sdk, restate-sdk-macros, restate-sdk-testcontainers
dependents
ecosystemscrates
total_downloads796,921
monthly_downloads201,626
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?

73Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.7/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth10 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.615
How it's scored
33.9/42Issue resolution81% of issues closed
26.1/30PR acceptance73/84 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 11/30 approved changesets -- score normalized to 3
Inputs used
merged_prs73
open_issues7
closed_issues29
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.806
closed_unmerged_prs11
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
18.1/25Owner reach327 followers of restatedev
22.1/25Track record82 public repos, account ~4 yr old
Inputs used
followers327
owner_typeOrganization
is_verified
owner_loginrestatedev
public_repos82
account_age_days1,655
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on crates
35/35Publish recencylatest publish 0 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrestate-sdk, restate-sdk-macros, restate-sdk-testcontainers
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://restate.dev/
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsdurable-execution, durable-functions, durable-objects, event-driven, workflows-as-code
has_wikino
homepagehttps://restate.dev/
docs_sitehttps://restate.dev/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 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
2.5/2.5CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 11/30 approved changesets -- score normalized to 3
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
7.5/7.5Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages34
affected_by_severitynone
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 1 resolved dependencies against OSV. 34 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.

68Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.5/40Legible commit history59 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.59
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapjustfile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice7 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_filesjustfile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.07
toolchain_manifestsCargo.toml, macros/Cargo.toml, test-services/Cargo.toml, testcontainers/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/76 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes47,459
source_files_sampled76
oversized_source_files0
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

83GitHub stars
10contributors
41commits, last 12 months
0days since last push
11releases
1bus factor
7open issues
crates.iopackage ecosystems

Data collection warnings

  • Could not fetch crates package 'test-services' from its registry
  • deps.dev does not index crates:restate-sdk@0.11.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 83 ★ / 25 ⇿
83Stars
25Forks
10Releases

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.

020406080100832432024-082025-082026-07
Major 0Minor 9Patch 1

Each point covers 2 days.

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-22 02:13 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests21 out of 21 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 11/30 approved changesets -- score normalized to 3
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
10Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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 45
RegistryPackageVersion constraintManifest
crates.iobytes1.11Cargo.toml
crates.iofutures0.3Cargo.toml
crates.iohttp1.4Cargo.toml
crates.iohttp-body1.0.1Cargo.toml
crates.iohttp-body-util0.1Cargo.toml
crates.iohyper1.8Cargo.toml
crates.iohyper-util0.1Cargo.toml
crates.iopin-project-lite0.2Cargo.toml
crates.iorand0.10Cargo.toml
crates.ioregress0.10Cargo.toml
crates.iorestate-sdk-macros0.11Cargo.toml
crates.iorestate-sdk-shared-core=7.0.1Cargo.toml
crates.ioschemars1.2Cargo.toml
crates.ioserde1.0Cargo.toml
crates.ioserde_json1.0Cargo.toml
crates.iothiserror2.0Cargo.toml
crates.iotokio1.49Cargo.toml
crates.iotracing0.1Cargo.toml
crates.iotracing-subscriber0.3Cargo.toml
crates.iouuid1.20Cargo.toml
crates.iohttp-serde2.1.1Cargo.toml
crates.ioaws_lambda_events1.0Cargo.toml
crates.iolambda_runtime1.0Cargo.toml
crates.iojiff0.2macros/Cargo.toml
crates.ioproc-macro21.0macros/Cargo.toml
crates.ioquote1.0macros/Cargo.toml
crates.iosyn2.0macros/Cargo.toml
crates.ioanyhow1.0test-services/Cargo.toml
crates.iobytes1.10.1test-services/Cargo.toml
crates.iotokio1test-services/Cargo.toml
crates.iotracing-subscriber0.3test-services/Cargo.toml
crates.iofutures0.3test-services/Cargo.toml
crates.iorestate-sdktest-services/Cargo.toml
crates.ioschemars1.0.0-alpha.17test-services/Cargo.toml
crates.ioserde1test-services/Cargo.toml
crates.iotracing0.1.40test-services/Cargo.toml
crates.ioanyhow1.0testcontainers/Cargo.toml
crates.iofutures0.3testcontainers/Cargo.toml
crates.ioreqwest0.13testcontainers/Cargo.toml
crates.iorestate-sdk0.11.0testcontainers/Cargo.toml
crates.ioserde1.0testcontainers/Cargo.toml
crates.iotestcontainers0.27testcontainers/Cargo.toml
crates.iotokio1.49testcontainers/Cargo.toml
crates.iotracing0.1testcontainers/Cargo.toml
crates.iotracing-subscriber0.3testcontainers/Cargo.toml
All dependencies 35

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

RegistryPackageVersionRelation
crates.ioanyhowdirect
crates.ioaws_lambda_eventsdirect
crates.iobytesdirect
crates.iofuturesdirect
crates.iohttpdirect
crates.iohttp-bodydirect
crates.iohttp-body-utildirect
crates.iohttp-serdedirect
crates.iohyperdirect
crates.iohyper-utildirect
crates.iojiffdirect
crates.iolambda_runtimedirect
crates.iopin-project-litedirect
crates.ioproc-macro2direct
crates.ioquotedirect
crates.ioranddirect
crates.ioregressdirect
crates.ioreqwestdirect
crates.iorestate-sdkdirect
crates.iorestate-sdk-macrosdirect
crates.iorestate-sdk-shared-core7.0.1direct
crates.ioschemarsdirect
crates.ioserdedirect
crates.ioserde_jsondirect
crates.iosyndirect
crates.iotestcontainersdirect
crates.iothiserrordirect
crates.iotokiodirect
crates.iotracingdirect
crates.iotracing-subscriberdirect
crates.iouuiddirect
crates.iojsonptrindirect
crates.ioprettypleaseindirect
crates.iotrybuildindirect
crates.iotypifyindirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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.26.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.