Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-23 00:29 UTC

0xMiden / crypto

Cryptographic primitives used in Polygon Miden rollup

RustApache-2.0★ 136 stars⑂ 98 forkssince Oct 2022archivedView on GitHub ↗
KindLibraryCommand-line toolhow this is determined

0xMiden/crypto holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on AI Readiness (79/100) and lowest on Community & Adoption (66/100). The repository is archived, so no further maintenance is expected.

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

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

Ownership

MidenOrganization
484 followers62 public repossince Dec 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iomiden-fieldpoints to another repo — not scored0.36.229,474340 days agocryptohashmerklemidencryptographyno-std
crates.iomiden-cryptopoints to another repo — not scored0.36.247,3731030 days agocryptohashmerklemidencryptographyno-std
crates.iomiden-serde-utilspoints to another repo — not scored0.36.230,368410 days agocryptohashmerklemidencryptographyno-std
crates.iomiden-crypto-derivepoints to another repo — not scored0.36.232,215560 days agocryptohashmerklemidencryptographyno-std
crates.iomiden-lifted-airpoints to another repo — not scored0.36.225,122260 days ago—
crates.iomiden-lifted-starkpoints to another repo — not scored0.36.225,112260 days ago—
crates.iomiden-stateful-hasherpoints to another repo — not scored0.36.225,120260 days ago—
crates.iomiden-stark-transcriptpoints to another repo — not scored0.36.225,125260 days ago—

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
18/36Push recency — last push 83 days ago
27/36Commit cadence — 39/52 weeks with commits
18/18Commit volume — 385 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year385
human_commit_share0.87
days_since_last_push83
active_weeks_last_year39

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 78 releases published
36/36Release recency — latest release 83 days ago
27/27Release cadence — a release every ~15.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count78
latest_release_tagv0.28.1
releases_from_tagsno
days_since_latest_release83
mean_days_between_releases15.6
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?

66Good · 17% of overall
How it's scored
34.6/60Stars — 136 stars
16.6/25Forks — 98 forks
6.2/15Watchers — 14 watchers
Inputs used
forks98
stars136
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
13.9/22.5Commit distribution — top contributor authored 38% of commits
13.5/13.5Contributor breadth — 54 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled54
top_contributor_share0.381
How it's scored
42/42Issue resolution — 100% of issues closed
24.3/30PR acceptance — 535/661 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 13/18 approved changesets -- score normalized to 7
Inputs used
merged_prs535
open_issues0
closed_issues243
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs126
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.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
19.3/25Owner reach — 484 followers of 0xMiden
16.8/25Track record — 62 public repos, account ~1 yr old
Inputs used
followers484
owner_typeOrganization
is_verifiedno
owner_login0xMiden
public_repos62
account_age_days686

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 12 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([workspace.lints]), benches/smt-codspeed/Cargo.toml ([lints]), miden-bench/Cargo.toml ([lints]), miden-crypto-derive/Cargo.toml ([lints]), miden-crypto-fuzz/Cargo.toml ([lints]), miden-crypto/Cargo.toml ([lints]), miden-field/Cargo.toml ([lints]), miden-serde-utils/Cargo.toml ([lints]), rustfmt.toml, stark/miden-lifted-air/Cargo.toml ([lints]), stark/miden-lifted-stark/Cargo.toml ([lints]), stark/miden-stark-transcript/Cargo.toml ([lints]), stark/miden-stateful-hasher/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 23 out of 23 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://0xmiden.github.io/crypto/
10/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicscryptography
has_wikino
homepagehttps://0xmiden.github.io/crypto/
docs_sitehttps://0xmiden.github.io/crypto/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
1.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 23 out of 23 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
5.2/7.5Code-Review — Found 13/18 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 16 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project is archived
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

79Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 84 of 87 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.966
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — Cargo.toml ([workspace.lints]), benches/smt-codspeed/Cargo.toml ([lints]), miden-bench/Cargo.toml ([lints]), miden-crypto-derive/Cargo.toml ([lints]), miden-crypto-fuzz/Cargo.toml ([lints]), miden-crypto/Cargo.toml ([lints]), miden-field/Cargo.toml ([lints]), miden-serde-utils/Cargo.toml ([lints]), rustfmt.toml, stark/miden-lifted-air/Cargo.toml ([lints]), stark/miden-lifted-stark/Cargo.toml ([lints]), stark/miden-stark-transcript/Cargo.toml ([lints]), stark/miden-stateful-hasher/Cargo.toml ([lints])
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 21 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 13 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.21
toolchain_manifestsCargo.toml, benches/smt-codspeed/Cargo.toml, miden-bench/Cargo.toml, miden-crypto-derive/Cargo.toml, miden-crypto-fuzz/Cargo.toml, miden-crypto/Cargo.toml, miden-field/Cargo.toml, miden-serde-utils/Cargo.toml, miden-serde-utils/fuzz/Cargo.toml, stark/miden-lifted-air/Cargo.toml, stark/miden-lifted-stark/Cargo.toml, stark/miden-stark-transcript/Cargo.toml, stark/miden-stateful-hasher/Cargo.toml, tests/wycheproof/Cargo.toml, tools/zeroize-audit/Cargo.toml
dependency_bot_commit_share0.13
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.6/55Manageable file sizes — 8/304 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes168,991
source_files_sampled304
oversized_source_files8

Key facts

136GitHub stars
54contributors
385commits, last 12 months
83days since last push
78releases
3bus 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 'miden-bench' from its registry
  • crates package 'miden-field' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • crates package 'miden-crypto' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • Could not fetch crates package 'miden-crypto-fuzz' from its registry
  • crates package 'miden-serde-utils' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • crates package 'miden-crypto-derive' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • Could not fetch crates package 'zeroize-audit' from its registry
  • Could not fetch crates package 'miden-crypto-smt-codspeed-bench' from its registry
  • crates package 'miden-lifted-air' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • crates package 'miden-lifted-stark' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • crates package 'miden-stateful-hasher' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring
  • crates package 'miden-stark-transcript' points at a different repository (https://github.com/0xMiden/miden-vm); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 98 ⇿
0Stars
98Forks
71Releases

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.

0204060801009742023-062025-012026-09
Major 0Minor 23Patch 48

Each point covers 3 days.

OpenSSF Scorecard 6.9 / 10
6.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-10-23 00:28 UTC

10Binary-Artifactsno binaries found in the repo
2Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 13/18 approved changesets -- score normalized to 7
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
8SASTSAST tool is not run on all commits -- score normalized to 8
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 103
RegistryPackageVersion constraintManifest
crates.iomiden-lifted-stark—miden-bench/Cargo.toml
crates.iop3-air—miden-bench/Cargo.toml
crates.iop3-batch-stark—miden-bench/Cargo.toml
crates.iop3-blake3—miden-bench/Cargo.toml
crates.iop3-blake3-air—miden-bench/Cargo.toml
crates.iop3-commit—miden-bench/Cargo.toml
crates.iop3-dft—miden-bench/Cargo.toml
crates.iop3-field—miden-bench/Cargo.toml
crates.iop3-fri—miden-bench/Cargo.toml
crates.iop3-goldilocks—miden-bench/Cargo.toml
crates.iop3-keccak—miden-bench/Cargo.toml
crates.iop3-keccak-air—miden-bench/Cargo.toml
crates.iop3-lookup—miden-bench/Cargo.toml
crates.iop3-matrix—miden-bench/Cargo.toml
crates.iop3-merkle-tree—miden-bench/Cargo.toml
crates.iop3-poseidon2-air—miden-bench/Cargo.toml
crates.iop3-symmetric—miden-bench/Cargo.toml
crates.iop3-uni-stark—miden-bench/Cargo.toml
crates.ioclap—miden-bench/Cargo.toml
crates.iopostcard—miden-bench/Cargo.toml
crates.iorand—miden-bench/Cargo.toml
crates.iotracing—miden-bench/Cargo.toml
crates.iotracing-forest—miden-bench/Cargo.toml
crates.iotracing-subscriber—miden-bench/Cargo.toml
crates.ioquote—miden-crypto-derive/Cargo.toml
crates.iosyn—miden-crypto-derive/Cargo.toml
crates.iolibfuzzer-sys0.4miden-crypto-fuzz/Cargo.toml
crates.iomiden-crypto—miden-crypto-fuzz/Cargo.toml
crates.iorand0.10miden-crypto-fuzz/Cargo.toml
crates.iomiden-crypto-derive—miden-crypto/Cargo.toml
crates.iomiden-field—miden-crypto/Cargo.toml
crates.iomiden-lifted-stark—miden-crypto/Cargo.toml
crates.iomiden-serde-utils—miden-crypto/Cargo.toml
crates.ioblake3—miden-crypto/Cargo.toml
crates.iochacha20poly1305—miden-crypto/Cargo.toml
crates.ioclap—miden-crypto/Cargo.toml
crates.iocurve25519-dalek—miden-crypto/Cargo.toml
crates.ioder—miden-crypto/Cargo.toml
crates.ioed25519-dalek—miden-crypto/Cargo.toml
crates.ioflume—miden-crypto/Cargo.toml
crates.iohkdf—miden-crypto/Cargo.toml
crates.iok256—miden-crypto/Cargo.toml
crates.ionum—miden-crypto/Cargo.toml
crates.ionum-complex—miden-crypto/Cargo.toml
crates.ioonce_cell—miden-crypto/Cargo.toml
crates.ioproptest—miden-crypto/Cargo.toml
crates.iorand—miden-crypto/Cargo.toml
crates.iorand_chacha—miden-crypto/Cargo.toml
crates.iorayon—miden-crypto/Cargo.toml
crates.iorocksdb—miden-crypto/Cargo.toml
crates.ioserde—miden-crypto/Cargo.toml
crates.iosha2—miden-crypto/Cargo.toml
crates.iosha3—miden-crypto/Cargo.toml
crates.iosubtle—miden-crypto/Cargo.toml
crates.iothiserror—miden-crypto/Cargo.toml
crates.iox25519-dalek—miden-crypto/Cargo.toml
crates.iop3-blake3—miden-crypto/Cargo.toml
crates.iop3-challenger—miden-crypto/Cargo.toml
crates.iop3-dft—miden-crypto/Cargo.toml
crates.iop3-goldilocks—miden-crypto/Cargo.toml
crates.iop3-keccak—miden-crypto/Cargo.toml
crates.iop3-matrix—miden-crypto/Cargo.toml
crates.iop3-maybe-rayon—miden-crypto/Cargo.toml
crates.iop3-symmetric—miden-crypto/Cargo.toml
crates.iop3-util—miden-crypto/Cargo.toml
crates.iothiserror—miden-field/Cargo.toml
crates.iop3-field—miden-serde-utils/Cargo.toml
crates.iop3-goldilocks—miden-serde-utils/Cargo.toml
crates.iop3-air—stark/miden-lifted-air/Cargo.toml
crates.iop3-challenger—stark/miden-lifted-air/Cargo.toml
crates.iop3-field—stark/miden-lifted-air/Cargo.toml
crates.iop3-matrix—stark/miden-lifted-air/Cargo.toml
crates.iop3-util—stark/miden-lifted-air/Cargo.toml
crates.iothiserror—stark/miden-lifted-air/Cargo.toml
crates.iomiden-lifted-air—stark/miden-lifted-stark/Cargo.toml
crates.iomiden-stark-transcript—stark/miden-lifted-stark/Cargo.toml
crates.iomiden-stateful-hasher—stark/miden-lifted-stark/Cargo.toml
crates.iop3-challenger—stark/miden-lifted-stark/Cargo.toml
crates.iop3-dft—stark/miden-lifted-stark/Cargo.toml
crates.iop3-field—stark/miden-lifted-stark/Cargo.toml
crates.iop3-goldilocks—stark/miden-lifted-stark/Cargo.toml
crates.iop3-matrix—stark/miden-lifted-stark/Cargo.toml
crates.iop3-maybe-rayon—stark/miden-lifted-stark/Cargo.toml
crates.iop3-symmetric—stark/miden-lifted-stark/Cargo.toml
crates.iop3-util—stark/miden-lifted-stark/Cargo.toml
crates.iop3-blake3—stark/miden-lifted-stark/Cargo.toml
crates.iop3-blake3-air—stark/miden-lifted-stark/Cargo.toml
crates.iop3-keccak—stark/miden-lifted-stark/Cargo.toml
crates.iop3-keccak-air—stark/miden-lifted-stark/Cargo.toml
crates.iop3-poseidon2-air—stark/miden-lifted-stark/Cargo.toml
crates.iorand—stark/miden-lifted-stark/Cargo.toml
crates.ioserde—stark/miden-lifted-stark/Cargo.toml
crates.iothiserror—stark/miden-lifted-stark/Cargo.toml
crates.iotracing—stark/miden-lifted-stark/Cargo.toml
crates.iop3-challenger—stark/miden-stark-transcript/Cargo.toml
crates.iop3-field—stark/miden-stark-transcript/Cargo.toml
crates.ioserde—stark/miden-stark-transcript/Cargo.toml
crates.iothiserror—stark/miden-stark-transcript/Cargo.toml
crates.iop3-field—stark/miden-stateful-hasher/Cargo.toml
crates.iop3-symmetric—stark/miden-stateful-hasher/Cargo.toml
crates.ioregex1.11tools/zeroize-audit/Cargo.toml
crates.ioserde1.0tools/zeroize-audit/Cargo.toml
crates.ioserde_json1.0tools/zeroize-audit/Cargo.toml
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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 statistics — crates.io.