Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-31 05:29 UTC

facebook / winterfell

A STARK prover and verifier for arbitrary computations

RustMIT★ 900 stars⑂ 232 forkssince Apr 2021View on GitHub ↗

facebook/winterfell holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (79/100) and lowest on Vitality (25/100). It was last updated 376 days ago. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

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

Ownership

MetaOrganization
36,334 followers168 public repossince Apr 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iowinter-airpoints to another repo — not scored0.13.156,56633376 days agocryptoairarithmetizationcryptographyno-std
crates.iowinter-fripoints to another repo — not scored0.13.156,49827376 days agocryptopolynomialcommitmentscryptographyno-std
crates.iowinter-mathpoints to another repo — not scored0.13.159,97429376 days agocryptofftpolynomialsfinite-fieldscryptographyno-std
crates.iowinter-cryptopoints to another repo — not scored0.13.159,42227376 days agohashcryptomerkle-treecryptographyno-std
crates.iowinter-proverpoints to another repo — not scored0.13.155,14429376 days agocryptoproverzkpstarkcryptographyno-std
crates.iowinter-verifierpoints to another repo — not scored0.13.154,80028376 days agocryptozkpstarkverifiercryptographyno-std
crates.iowinterfellpoints to another repo — not scored0.13.122,38528376 days agocryptoproverzkpstarkverifiercryptographyno-std
crates.iowinter-utilspoints to another repo — not scored0.13.160,17835376 days agoserializationtransmutecryptographyno-std
crates.iowinter-rand-utilspoints to another repo — not scored0.13.119,43823376 days agorandcryptography
crates.iowinter-maybe-async0.13.145,7377376 days agoasync

Metrics by category

Vitality

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

25At Risk · 21% of overall
How it's scored
0/36Push recencylast push 376 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push376
active_weeks_last_year0
How it's scored
27/27Ships releases28 releases published
7.2/36Release recencylatest release 376 days ago
19.8/27Release cadencea release every ~48.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count28
latest_release_tagv0.13.1
releases_from_tagsno
days_since_latest_release376
mean_days_between_releases48.4
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?

79Good · 17% of overall
How it's scored
47.9/60Stars900 stars
19.7/25Forks232 forks
7.8/15Watchers26 watchers
Inputs used
forks232
stars900
watchers26
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
62.1/80Monthly downloads45,737 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageswinter-maybe-async
dependents
ecosystemscrates
total_downloads451,432
monthly_downloads45,737
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?

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.4/22.5Commit distributiontop contributor authored 72% of commits
13.5/13.5Contributor breadth35 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled35
top_contributor_share0.716
How it's scored
24.4/42Issue resolution58% of issues closed
24.7/30PR acceptance227/276 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 10/30 approved changesets -- score normalized to 3
Inputs used
merged_prs227
open_issues49
closed_issues68
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.581
closed_unmerged_prs49
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
25/25Owner reach36,334 followers of facebook
25/25Track record168 public repos, account ~17 yr old
Inputs used
followers36,334
owner_typeOrganization
is_verified
owner_loginfacebook
public_repos168
account_age_days6,329
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on crates
14/35Publish recencylatest publish 376 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageswinter-maybe-async
ecosystemscrates
any_deprecatedno
min_days_since_publish376

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
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://docs.rs/winter-maybe-async
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/winter-maybe-async
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 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
0/2.5CI-Tests0 out of 11 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
2.2/7.5Code-ReviewFound 10/30 approved changesets -- score normalized to 3
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
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
4.5/5Security-Policysecurity policy file 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Packaging, 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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages36
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the crates:winterfell@0.13.1 runtime dependency closure — what installing the published package pulls in — 36 packages. 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.9/40Legible commit history41 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.41
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
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
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, air/Cargo.toml, crypto/Cargo.toml, examples/Cargo.toml, fri/Cargo.toml, math/Cargo.toml, prover/Cargo.toml, utils/core/Cargo.toml, utils/maybe_async/Cargo.toml, utils/rand/Cargo.toml, verifier/Cargo.toml, winterfell/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/199 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes46,744
source_files_sampled199
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

900GitHub stars
35contributors
0commits, last 12 months
376days since last push
28releases
1bus factor
49open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'winter-air' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-fri' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-math' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-crypto' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-prover' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-verifier' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winterfell' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-utils' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring
  • crates package 'winter-rand-utils' points at a different repository (https://github.com/novifinancial/winterfell); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 232 ⇿
0Stars
232Forks
28Releases

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.

0408012016020024021472021-042023-122026-07
Major 0Minor 10Patch 18

Each point covers 5 days.

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-07-31 05:28 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/30 approved changesets -- score normalized to 3
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 33
RegistryPackageVersion constraintManifest
crates.iocrypto0.13air/Cargo.toml
crates.iofri0.13air/Cargo.toml
crates.iolibm0.2air/Cargo.toml
crates.iomath0.13air/Cargo.toml
crates.ioutils0.13air/Cargo.toml
crates.ioblake31.8crypto/Cargo.toml
crates.iomath0.13crypto/Cargo.toml
crates.iosha30.10crypto/Cargo.toml
crates.ioutils0.13crypto/Cargo.toml
crates.iocrypto0.13fri/Cargo.toml
crates.iomath0.13fri/Cargo.toml
crates.ioutils0.13fri/Cargo.toml
crates.ioserde1.0math/Cargo.toml
crates.ioutils0.13math/Cargo.toml
crates.ioair0.13prover/Cargo.toml
crates.iocrypto0.13prover/Cargo.toml
crates.iofri0.13prover/Cargo.toml
crates.iomath0.13prover/Cargo.toml
crates.iomaybe_async0.13prover/Cargo.toml
crates.iotracing0.1prover/Cargo.toml
crates.ioutils0.13prover/Cargo.toml
crates.ioair0.13verifier/Cargo.toml
crates.iocrypto0.13verifier/Cargo.toml
crates.iofri0.13verifier/Cargo.toml
crates.iomath0.13verifier/Cargo.toml
crates.ioutils0.13verifier/Cargo.toml
crates.ioair0.13winterfell/Cargo.toml
crates.ioprover0.13winterfell/Cargo.toml
crates.ioverifier0.13winterfell/Cargo.toml
crates.iorayon1.10utils/core/Cargo.toml
crates.ioquote1utils/maybe_async/Cargo.toml
crates.iosyn2utils/maybe_async/Cargo.toml
crates.ioutils0.13utils/rand/Cargo.toml
All dependencies 26

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

RegistryPackageVersionRelation
crates.ioblake3direct
crates.iolibmdirect
crates.ioquotedirect
crates.iorayondirect
crates.ioserdedirect
crates.iosha3direct
crates.iosyndirect
crates.iotracingdirect
crates.iocriterionindirect
crates.iohexindirect
crates.ionum-bigintindirect
crates.ioproptestindirect
crates.iorandindirect
crates.iostructoptindirect
crates.iotracing-forestindirect
crates.iotracing-subscriberindirect
crates.iowinter-airindirect
crates.iowinter-cryptoindirect
crates.iowinter-friindirect
crates.iowinter-mathindirect
crates.iowinter-maybe-asyncindirect
crates.iowinter-proverindirect
crates.iowinter-rand-utilsindirect
crates.iowinter-utilsindirect
crates.iowinter-verifierindirect
crates.iowinterfellindirect
Dependency advisories 0

Installing crates:winterfell@0.13.1 pulls in 36 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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

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