Public record
Software health reportschema 0.13.0 · metrics 2.10.0 · 2026-07-18 15:31 UTC

input-output-hk / rust-cardano

rust client libraries to deal with the current cardano mainnet (byron / cardano-sl)

Rust · CMIT★ 266 stars⑂ 74 forkssince Feb 2018archivedView on GitHub ↗

input-output-hk/rust-cardano holds a health index of 17 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (74/100) and lowest on Vitality (13/100). The repository is archived, so no further maintenance is expected.

17
overall / 100
Critical

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.

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

Ownership

Input OutputOrganization
1,197 followers757 public repossince Jun 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iocardanopoints to another repo — not scored0.4.025410 days ago
crates.ioprotocolpoints to another repo — not scored3.4.01,997711406 days agoudpprotocolconnectiontcpencoding

Metrics by category

Vitality

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

13Critical · 21% of overall
How it's scored
0/36Push recencylast push 1,498 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year0
human_commit_share
days_since_last_push1,498
active_weeks_last_year0
How it's scored
16.2/27Ships releases1 version tags (no GitHub releases)
0/36Release recencylatest release 3,049 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv0.1.2
releases_from_tagsyes
days_since_latest_release3,049
mean_days_between_releases
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?

64Moderate · 17% of overall
How it's scored
39.3/60Stars266 stars
15.5/25Forks74 forks
3.3/15Watchers5 watchers
Inputs used
forks74
stars266
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

74Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11.1/22.5Commit distributiontop contributor authored 51% of commits
13.5/13.5Contributor breadth24 contributors
10/10OpenSSF Scorecard: Contributorsproject has 31 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled24
top_contributor_share0.507
How it's scored
42/42Issue resolution100% of issues closed
28.3/30PR acceptance554/588 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 6/14 approved changesets -- score normalized to 4
Inputs used
merged_prs554
open_issues0
closed_issues143
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs34
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
22.1/25Owner reach1,197 followers of input-output-hk
25/25Track record757 public repos, account ~11 yr old
Inputs used
followers1,197
owner_typeOrganization
is_verified
owner_logininput-output-hk
public_repos757
account_age_days4,050
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

37Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 6/14 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 31 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject is archived
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

59Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapcardano-c/examples/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filescardano-c/examples/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeRust (statically typed)
53.9/55Manageable file sizes3/155 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes81,700
source_files_sampled155
oversized_source_files3
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

266GitHub stars
24contributors
0commits, last 12 months
1,498days since last push
1releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • Could not fetch crates package 'cardano-c' from its registry
  • crates package 'cardano' points at a different repository (https://github.com/valkyoth/cardano); excluded from ecosystem scoring
  • Could not fetch crates package 'chain-core' from its registry
  • Could not fetch crates package 'exe-common' from its registry
  • Could not fetch crates package 'network-core' from its registry
  • Could not fetch crates package 'network-ntt' from its registry
  • Could not fetch crates package 'protocol-tokio' from its registry
  • crates package 'protocol' points at a different repository (https://github.com/dylanmckay/protocol); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-18 15:31 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
0CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 6/14 approved changesets -- score normalized to 4
10Contributorsproject has 31 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 54
RegistryPackageVersion constraintManifest
crates.iocardanocardano-c/Cargo.toml
crates.iocbor_event^2.1.1cardano-c/Cargo.toml
crates.iocryptoxide0.1cardano/Cargo.toml
crates.iocbor_event^2.1.1cardano/Cargo.toml
crates.iochain-corecardano/Cargo.toml
crates.ioserde1.0cardano/Cargo.toml
crates.ioserde_derive1.0cardano/Cargo.toml
crates.iocfg-if0.1chain-core/Cargo.toml
crates.ioquickcheck0.8chain-core/Cargo.toml
crates.iocardano-storageexe-common/Cargo.toml
crates.iostorage-unitsexe-common/Cargo.toml
crates.ioprotocolexe-common/Cargo.toml
crates.iocbor_event2.1.2exe-common/Cargo.toml
crates.iolog*exe-common/Cargo.toml
crates.iorand0.6exe-common/Cargo.toml
crates.ioserde1.0exe-common/Cargo.toml
crates.ioserde_derive1.0exe-common/Cargo.toml
crates.ioserde_yaml0.7exe-common/Cargo.toml
crates.ioserde_json1.0exe-common/Cargo.toml
crates.iobase640.9exe-common/Cargo.toml
crates.ionetwork-nttexe-common/Cargo.toml
crates.ionetwork-coreexe-common/Cargo.toml
crates.iofutures0.1exe-common/Cargo.toml
crates.iohyper0.11exe-common/Cargo.toml
crates.iotokio0.1.15exe-common/Cargo.toml
crates.iotokio-core0.1.15exe-common/Cargo.toml
crates.iocardanoexe-common/Cargo.toml
crates.iochain-corenetwork-core/Cargo.toml
crates.iobytes0.4network-core/Cargo.toml
crates.iofutures0.1network-core/Cargo.toml
crates.ioslog^2.4.1network-ntt/Cargo.toml
crates.iofutures^0.1network-ntt/Cargo.toml
crates.iotokio^0.1network-ntt/Cargo.toml
crates.ionetwork-corenetwork-ntt/Cargo.toml
crates.iochain-corenetwork-ntt/Cargo.toml
crates.ioprotocol-tokionetwork-ntt/Cargo.toml
crates.iocbor_event^2.1network-ntt/Cargo.toml
crates.iocbor_event^2.1.1protocol-tokio/Cargo.toml
crates.iofutures^0.1.25protocol-tokio/Cargo.toml
crates.iotokio-io^0.1.9protocol-tokio/Cargo.toml
crates.iotokio-codec^0.1.1protocol-tokio/Cargo.toml
crates.iobytes^0.4.10protocol-tokio/Cargo.toml
crates.iolog^0.4.5protocol-tokio/Cargo.toml
crates.iochain-coreprotocol-tokio/Cargo.toml
crates.iocbor_event^2.1.2protocol/Cargo.toml
crates.iocardanoprotocol/Cargo.toml
crates.iolog0.4protocol/Cargo.toml
crates.iorand0.6storage-units/Cargo.toml
crates.iocryptoxide0.1storage-units/Cargo.toml
crates.iocardanostorage/Cargo.toml
crates.iocbor_event^2.1.1storage/Cargo.toml
crates.iostorage-unitsstorage/Cargo.toml
crates.iolog*storage/Cargo.toml
crates.iorand0.6storage/Cargo.toml
All dependencies 20

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

RegistryPackageVersionRelation
crates.iobase64direct
crates.iobytesdirect
crates.iocbor_eventdirect
crates.iocryptoxidedirect
crates.iofuturesdirect
crates.iohyperdirect
crates.iologdirect
crates.ioquickcheckdirect
crates.ioranddirect
crates.ioserdedirect
crates.ioserde_derivedirect
crates.ioserde_jsondirect
crates.ioserde_yamldirect
crates.iotokiodirect
crates.iotokio-codecdirect
crates.iotokio-coredirect
crates.iotokio-iodirect
crates.ioenv_loggerindirect
crates.iolazy_staticindirect
crates.iounicode-normalizationindirect
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.13.0 — full methodology · metrics wiki.

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