Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-02 12:57 UTC

Stoffel-Labs / mpc-protocols

MPC Protocols for the Stoffel framework

RustApache-2.0★ 14 stars⑂ 0 forkssince Mar 2025View on GitHub ↗
KindLibraryhow this is determined
#confidential-computing#crypto#cryptography#cryptography-library#mpc#multi-party-computation#multiparty-computation#privacy#privacy-enhancing-technologies#privacy-preserving#privacy-preserving-computing#secret-sharing#secret-sharing-scheme#secret-sharing-shamir#secure-computation#secure-multi-party-computation#security#security-protocol#smpc#threshold-cryptography

Stoffel-Labs/mpc-protocols holds a health index of 75 out of 100, placing it in the Good band. It scores highest on AI Readiness (82/100) and lowest on Community & Adoption (40/100). It was last updated today. 2 contributors account for most of its recent work.

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

75
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 65 is calibrated to 75 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

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iostoffelcrypto0.1.12,51424 days agocryptocryptographyasyncmpcsecret-sharing
crates.iostoffelmpc-network0.1.12,52224 days agotestingnetworksimulationmpcinternalcryptographynetwork-programming

Metrics by category

Vitality

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

81Excellent · 21% of overall

Development activity

79Good
How it's scored
36/36Push recency — last push 0 days ago
17.3/36Commit cadence — 25/52 weeks with commits
15.6/18Commit volume — 54 commits in the last year
10/10OpenSSF Scorecard: Maintained — 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year54
human_commit_share1
days_since_last_push0
active_weeks_last_year25

Release discipline

83Excellent
How it's scored
27/27Ships releases — 2 releases published
36/36Release recency — latest release 4 days ago
19.8/27Release cadence — a release every ~67.5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count2
latest_release_tagv0.1.1
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases67.5

Community & Adoption

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

40Weak · 17% of overall

Popularity & adoption

18Critical
How it's scored
18.1/60Stars — 14 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars14
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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

Ecosystem adoption (downloads)

62Moderate
How it's scored
49.4/80Monthly downloads — 5,036 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesstoffelcrypto, stoffelmpc-network
dependents—
ecosystemscrates
total_downloads15,110
monthly_downloads5,036
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?

68Good · 23% of overall

Maintainer resilience (bus factor)

58Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12/22.5Commit distribution — top contributor authored 47% of commits
10.8/13.5Contributor breadth — 8 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled8
top_contributor_share0.466

Issue & PR responsiveness

73Good
How it's scored
33.6/42Issue resolution — 80% of issues closed
23.5/30PR acceptance — 83/106 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 9/20 approved changesets -- score normalized to 4
Inputs used
merged_prs83
open_issues1
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.8
closed_unmerged_prs23
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

54Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
11.6/25Owner reach — 40 followers of Stoffel-Labs
12.7/25Track record — 16 public repos, account ~1 yr old
Inputs used
followers40
owner_typeOrganization
is_verifiedno
owner_loginStoffel-Labs
public_repos16
account_age_days686

Package maintenance

92Excellent
How it's scored
25/25Published & resolvable — 2 package(s) on crates
35/35Publish recency — latest publish 4 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesstoffelcrypto, stoffelmpc-network
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — mpc/Cargo.toml ([lints]), network/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 11 out of 11 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

65Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.stoffelmpc.com
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicsconfidential-computing, crypto, cryptography, cryptography-library, mpc, multi-party-computation, multiparty-computation, privacy, privacy-enhancing-technologies, privacy-preserving, privacy-preserving-computing, secret-sharing, secret-sharing-scheme, secret-sharing-shamir, secure-computation, secure-multi-party-computation, security, security-protocol, smpc, threshold-cryptography
has_wikino
homepagehttps://docs.stoffelmpc.com
docs_sitehttps://docs.stoffelmpc.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

46Weak · 16% of overall

Security posture

46Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 11 out of 11 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
3/7.5Code-Review — Found 9/20 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 4 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 — 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.6

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.

82Excellent · 4% of overall

Agent context & guidance

87Excellent
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.stoffelmpc.com/llms.txt)
27.2/40Legible commit history — 51 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.stoffelmpc.com/llms.txt
legible_history_share0.51
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes7,891

Verify loop (build / test / typecheck)

71Good
How it's scored
12.6/18One-command bootstrap — Cargo.toml, mpc/Cargo.toml, network/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — mpc/Cargo.toml ([lints]), network/Cargo.toml ([lints])
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
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_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifestsCargo.toml, mpc/Cargo.toml, network/Cargo.toml
dependency_bot_commit_share0

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.6/55Manageable file sizes — 3/114 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes112,626
source_files_sampled114
oversized_source_files3

Key facts

14GitHub stars
8contributors
54commits, last 12 months
0days since last push
2releases
2bus factor
1open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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-02 12:56 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 9/20 approved changesets -- score normalized to 4
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained22 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 44
RegistryPackageVersion constraintManifest
crates.iothiserror—mpc/Cargo.toml
crates.iotracing-subscriber—mpc/Cargo.toml
crates.iostoffelmpc-network0.1.1mpc/Cargo.toml
crates.ioark-ff—mpc/Cargo.toml
crates.ioserde—mpc/Cargo.toml
crates.ioark-serialize—mpc/Cargo.toml
crates.iotokio—mpc/Cargo.toml
crates.iotracing—mpc/Cargo.toml
crates.ioark-poly—mpc/Cargo.toml
crates.ioark-std—mpc/Cargo.toml
crates.ioark-bls12-381—mpc/Cargo.toml
crates.ioark-bn254—mpc/Cargo.toml
crates.iobincode—mpc/Cargo.toml
crates.iothreshold_crypto—mpc/Cargo.toml
crates.ioasync-trait—mpc/Cargo.toml
crates.iosha2—mpc/Cargo.toml
crates.iors_merkle—mpc/Cargo.toml
crates.ioreed-solomon-erasure—mpc/Cargo.toml
crates.iorand—mpc/Cargo.toml
crates.iofutures—mpc/Cargo.toml
crates.ioitertools—mpc/Cargo.toml
crates.iostoffelnet—mpc/Cargo.toml
crates.iorustls—mpc/Cargo.toml
crates.ionum-bigint—mpc/Cargo.toml
crates.iouuid—mpc/Cargo.toml
crates.ioark-ec—mpc/Cargo.toml
crates.iochacha20poly1305—mpc/Cargo.toml
crates.ionum-integer—mpc/Cargo.toml
crates.ioturmoil—mpc/Cargo.toml
crates.ionum-traits—mpc/Cargo.toml
crates.iothiserror—network/Cargo.toml
crates.ioserde—network/Cargo.toml
crates.ioark-serialize—network/Cargo.toml
crates.ioark-ff—network/Cargo.toml
crates.iotokio—network/Cargo.toml
crates.ioasync-trait—network/Cargo.toml
crates.iofutures—network/Cargo.toml
crates.iostoffelnet—network/Cargo.toml
crates.ioark-std—network/Cargo.toml
crates.iotracing—network/Cargo.toml
crates.ioonce_cell1.21.3network/Cargo.toml
crates.iotracing-subscriber0.3network/Cargo.toml
crates.ioturmoil—network/Cargo.toml
crates.iotime—network/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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with Stoffel-Labs/mpc-protocols. Read them side by side →

95actix/actix-netA collection of lower-level libraries for composable network services.Exceptional94plabayo/ramamodular service framework to move and transform network packetsExceptional94aws/aws-lc-rsaws-lc-rs is a cryptographic library using AWS-LC for its cryptographic operations. The library strives to be API-compatible with the popular Rust library named ring.Exceptional98tokio-rs/tokioA runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...Exceptional97rustls/rustlsA modern TLS library in RustExceptional96microsoft/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.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.