Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 03:29 UTC

Stoffel-Labs / stoffel-mpc-coordinator

Coordination of the execution of MPC programs managed by a smart contract or another entity.

RustApache-2.0★ 2 stars⑂ 0 forkssince Jan 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

Stoffel-Labs/stoffel-mpc-coordinator holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (33/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

56
overall / 100
Moderate

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.

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

Ownership

Stoffel LabsOrganization
40 followers16 public repossince Oct 2024

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

Package ecosystems

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
20.1/36Commit cadence29/52 weeks with commits
18/18Commit volume157 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year157
human_commit_share1
days_since_last_push5
active_weeks_last_year29
How it's scored
27/27Ships releases2 releases published
36/36Release recencylatest release 8 days ago
19.8/27Release cadencea release every ~67.2 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count2
latest_release_tagv0.2.0
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases67.2

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

33At Risk · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
49.5/80Monthly downloads5,133 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesstoffel-mpc-coordinator-off-chain, stoffel-mpc-coordinator-shared
dependents
ecosystemscrates
total_downloads15,401
monthly_downloads5,133
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7/22.5Commit distributiontop contributor authored 69% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.688
How it's scored
0/42Issue resolutionno issues or no data
18/30PR acceptance12/20 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 2/6 approved changesets -- score normalized to 3
Inputs used
merged_prs12
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d1
prs_merged_30d2
prs_decided_30d5
issue_closed_ratio
closed_unmerged_prs8
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
11.6/25Owner reach40 followers of Stoffel-Labs
12.7/25Track record16 public repos, account ~1 yr old
Inputs used
followers40
owner_typeOrganization
is_verifiedno
owner_loginStoffel-Labs
public_repos16
account_age_days690
How it's scored
25/25Published & resolvable2 package(s) on crates
35/35Publish recencylatest publish 5 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesstoffel-mpc-coordinator-off-chain, stoffel-mpc-coordinator-shared
ecosystemscrates
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests1 out of 2 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/stoffel-mpc-coordinator-off-chain
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://docs.rs/stoffel-mpc-coordinator-off-chain
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

39Weak · 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
1.2/2.5CI-Tests1 out of 2 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 2/6 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 5 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.5Maintained30 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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.9

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.

48Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
11.7/40Legible commit history22 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.22
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, crates/bins/Cargo.toml, crates/coord-shared/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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
lockfilesCargo.lock
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, crates/bins/Cargo.toml, crates/coord-shared/Cargo.toml, crates/off-chain/Cargo.toml, crates/on-chain/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
51.3/55Manageable file sizes1/15 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes122,196
source_files_sampled15
oversized_source_files1

Key facts

2GitHub stars
3contributors
157commits, last 12 months
5days since last push
2releases
1bus factor
0open 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 'stoffel-mpc-coordinator-bins' from its registry
  • Could not fetch crates package 'stoffel-mpc-coordinator-on-chain' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-06 03:29 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests1 out of 2 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 2/6 approved changesets -- score normalized to 3
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 75
RegistryPackageVersion constraintManifest
crates.iostoffel-mpc-coordinator-sharedcrates/bins/Cargo.toml
crates.iostoffel-mpc-coordinator-off-chaincrates/bins/Cargo.toml
crates.iostoffel-vm-typescrates/bins/Cargo.toml
crates.ioalloycrates/bins/Cargo.toml
crates.ioalloy-primitivescrates/bins/Cargo.toml
crates.iostoffel-solidity-bindings-testcrates/bins/Cargo.toml
crates.ioark-bls12-381crates/bins/Cargo.toml
crates.ioark-ffcrates/bins/Cargo.toml
crates.ioark-serializecrates/bins/Cargo.toml
crates.ioclapcrates/bins/Cargo.toml
crates.iohexcrates/bins/Cargo.toml
crates.iorcgencrates/bins/Cargo.toml
crates.iorustlscrates/bins/Cargo.toml
crates.iostoffelmpc-mpccrates/bins/Cargo.toml
crates.iotokiocrates/bins/Cargo.toml
crates.iox509-parsercrates/bins/Cargo.toml
crates.iostoffelmpc-mpccrates/coord-shared/Cargo.toml
crates.iostoffelnetcrates/coord-shared/Cargo.toml
crates.iotokiocrates/coord-shared/Cargo.toml
crates.ioark-bls12-381crates/coord-shared/Cargo.toml
crates.iojsonrpseecrates/coord-shared/Cargo.toml
crates.ioserdecrates/coord-shared/Cargo.toml
crates.ioark-ffcrates/coord-shared/Cargo.toml
crates.ioark-eccrates/coord-shared/Cargo.toml
crates.ioark-serializecrates/coord-shared/Cargo.toml
crates.iothiserrorcrates/coord-shared/Cargo.toml
crates.ioasync-traitcrates/coord-shared/Cargo.toml
crates.iofutures-utilcrates/coord-shared/Cargo.toml
crates.iorcgencrates/coord-shared/Cargo.toml
crates.iotowercrates/coord-shared/Cargo.toml
crates.iorustlscrates/coord-shared/Cargo.toml
crates.iotokio-rustlscrates/coord-shared/Cargo.toml
crates.iourlcrates/coord-shared/Cargo.toml
crates.ioringcrates/coord-shared/Cargo.toml
crates.iohypercrates/coord-shared/Cargo.toml
crates.iohyper-utilcrates/coord-shared/Cargo.toml
crates.iox509-parsercrates/coord-shared/Cargo.toml
crates.iohpkecrates/coord-shared/Cargo.toml
crates.iorandcrates/coord-shared/Cargo.toml
crates.iop256crates/coord-shared/Cargo.toml
crates.iotracingcrates/coord-shared/Cargo.toml
crates.iohexcrates/coord-shared/Cargo.toml
crates.iostoffel-mpc-coordinator-sharedcrates/off-chain/Cargo.toml
crates.ioark-ffcrates/off-chain/Cargo.toml
crates.ioark-serializecrates/off-chain/Cargo.toml
crates.ioark-bls12-381crates/off-chain/Cargo.toml
crates.ioasync-traitcrates/off-chain/Cargo.toml
crates.iofutures-utilcrates/off-chain/Cargo.toml
crates.iohpkecrates/off-chain/Cargo.toml
crates.iojsonrpseecrates/off-chain/Cargo.toml
crates.iop256crates/off-chain/Cargo.toml
crates.iorandcrates/off-chain/Cargo.toml
crates.iorcgencrates/off-chain/Cargo.toml
crates.ioserdecrates/off-chain/Cargo.toml
crates.iotokiocrates/off-chain/Cargo.toml
crates.iotracingcrates/off-chain/Cargo.toml
crates.iostoffel-mpc-coordinator-sharedcrates/on-chain/Cargo.toml
crates.ioalloycrates/on-chain/Cargo.toml
crates.ioalloy-primitivescrates/on-chain/Cargo.toml
crates.iostoffel-solidity-bindingscrates/on-chain/Cargo.toml
crates.ioark-bls12-381crates/on-chain/Cargo.toml
crates.ioark-ffcrates/on-chain/Cargo.toml
crates.ioark-serializecrates/on-chain/Cargo.toml
crates.ioasync-traitcrates/on-chain/Cargo.toml
crates.iofutures-utilcrates/on-chain/Cargo.toml
crates.iohpkecrates/on-chain/Cargo.toml
crates.iojsonrpseecrates/on-chain/Cargo.toml
crates.iop256crates/on-chain/Cargo.toml
crates.iorandcrates/on-chain/Cargo.toml
crates.iorcgencrates/on-chain/Cargo.toml
crates.ioserdecrates/on-chain/Cargo.toml
crates.iostoffelmpc-mpccrates/on-chain/Cargo.toml
crates.iothiserrorcrates/on-chain/Cargo.toml
crates.iotokiocrates/on-chain/Cargo.toml
crates.iotracingcrates/on-chain/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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 statisticscrates.io.