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

alloy-rs / eips

Rust implementations of Ethereum Improvement Proposals (EIPs)

RustApache-2.0★ 54 stars⑂ 25 forkssince Aug 2024View on GitHub ↗
KindLibraryhow this is determined

alloy-rs/eips holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Engineering Quality (72/100) and lowest on Vitality (51/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

AlloyOrganization
882 followers21 public repossince Mar 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.ioalloy-eip21240.2.01,535,0112526 days ago
crates.ioalloy-eip29300.2.41,664,813635 days ago
crates.ioalloy-eip77020.6.31,663,91815317 days ago
crates.ioalloy-eip79280.4.111,403,461221 day ago
crates.ioalloy-eip81410.1.19522 days ago

Metrics by category

Vitality

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

51Moderate · 21% of overall

Development activity

84Excellent
How it's scored
36/36Push recency — last push 1 days ago
20.8/36Commit cadence — 30/52 weeks with commits
17.7/18Commit volume — 92 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year92
human_commit_share0.95
days_since_last_push1
active_weeks_last_year30

Release discipline

1Critical
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

70Good · 17% of overall

Popularity & adoption

44Weak
How it's scored
28/60Stars — 54 stars
11.5/25Forks — 25 forks
4.3/15Watchers — 7 watchers
Inputs used
forks25
stars54
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

77Good
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Ecosystem adoption (downloads)

100Exceptional
How it's scored
80/80Monthly downloads — 6,267,298 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesalloy-eip2124, alloy-eip2930, alloy-eip7702, alloy-eip7928, alloy-eip8141
dependents—
ecosystemscrates
total_downloads60,675,803
monthly_downloads6,267,298
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?

69Good · 23% of overall

Maintainer resilience (bus factor)

43Weak
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.5/22.5Commit distribution — top contributor authored 53% of commits
13.5/13.5Contributor breadth — 21 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.532

Issue & PR responsiveness

78Good
How it's scored
36/42Issue resolution — 86% of issues closed
24/30PR acceptance — 99/124 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 10/27 approved changesets -- score normalized to 3
Inputs used
merged_prs99
open_issues1
closed_issues6
prs_merged_7d6
prs_decided_7d7
prs_merged_30d12
prs_decided_30d14
issue_closed_ratio0.857
closed_unmerged_prs25
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2

Ownership & stewardship

68Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
21.2/25Owner reach — 882 followers of alloy-rs
16.8/25Track record — 21 public repos, account ~3 yr old
Inputs used
followers882
owner_typeOrganization
is_verifiedno
owner_loginalloy-rs
public_repos21
account_age_days1,281

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 5 package(s) on crates
35/35Publish recency — latest publish 1 days ago
20/20Version history — 22 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesalloy-eip2124, alloy-eip2930, alloy-eip7702, alloy-eip7928, alloy-eip8141
ecosystemscrates
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([workspace.lints]), clippy.toml, crates/eip2124/Cargo.toml ([lints]), crates/eip2930/Cargo.toml ([lints]), crates/eip7702/Cargo.toml ([lints]), crates/eip7928/Cargo.toml ([lints]), crates/eip8141/Cargo.toml ([lints]), rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 22 out of 22 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

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/alloy-eip2124
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_sitehttps://docs.rs/alloy-eip2124
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

68Good · 16% of overall

Security posture

68Good
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 — 22 out of 22 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
2.2/7.5Code-Review — Found 10/27 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
1.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.8
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.

66Good · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 95 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

74Good
How it's scored
12.6/18One-command bootstrap — Cargo.toml, crates/eip2124/Cargo.toml, crates/eip2930/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — Cargo.toml ([workspace.lints]), clippy.toml, crates/eip2124/Cargo.toml ([lints]), crates/eip2930/Cargo.toml ([lints]), crates/eip7702/Cargo.toml ([lints]), crates/eip7928/Cargo.toml ([lints]), crates/eip8141/Cargo.toml ([lints]), rustfmt.toml
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, crates/eip2124/Cargo.toml, crates/eip2930/Cargo.toml, crates/eip7702/Cargo.toml, crates/eip7928/Cargo.toml, crates/eip8141/Cargo.toml
dependency_bot_commit_share0.05

Code legibility for models

98Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.3/55Manageable file sizes — 1/33 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes85,240
source_files_sampled33
oversized_source_files1

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 25 ⇿
0Stars
25Forks

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.

05101520252522024-082025-092026-09

Each point covers 2 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-18 03:18 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/27 approved changesets -- score normalized to 3
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
n/aPackagingpackaging workflow not detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
0SASTSAST tool is not run on all commits -- score normalized to 0
3Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 36
RegistryPackageVersion constraintManifest
crates.ioalloy-primitives—crates/eip2124/Cargo.toml
crates.ioalloy-rlp—crates/eip2124/Cargo.toml
crates.ioserde—crates/eip2124/Cargo.toml
crates.iocrc3crates/eip2124/Cargo.toml
crates.ioarbitrary—crates/eip2124/Cargo.toml
crates.iorand—crates/eip2124/Cargo.toml
crates.iothiserror—crates/eip2124/Cargo.toml
crates.ioalloy-primitives—crates/eip2930/Cargo.toml
crates.ioalloy-rlp—crates/eip2930/Cargo.toml
crates.ioserde—crates/eip2930/Cargo.toml
crates.ioborsh—crates/eip2930/Cargo.toml
crates.ioarbitrary—crates/eip2930/Cargo.toml
crates.iorand—crates/eip2930/Cargo.toml
crates.ioalloy-primitives—crates/eip7702/Cargo.toml
crates.ioalloy-rlp—crates/eip7702/Cargo.toml
crates.ioserde—crates/eip7702/Cargo.toml
crates.ioserde_with3crates/eip7702/Cargo.toml
crates.ioborsh—crates/eip7702/Cargo.toml
crates.ioarbitrary—crates/eip7702/Cargo.toml
crates.iok256—crates/eip7702/Cargo.toml
crates.iorand—crates/eip7702/Cargo.toml
crates.iothiserror—crates/eip7702/Cargo.toml
crates.ioalloy-primitives—crates/eip7928/Cargo.toml
crates.ioalloy-rlp—crates/eip7928/Cargo.toml
crates.ioonce_cell—crates/eip7928/Cargo.toml
crates.iothiserror—crates/eip7928/Cargo.toml
crates.ioserde—crates/eip7928/Cargo.toml
crates.ioborsh—crates/eip7928/Cargo.toml
crates.ioarbitrary—crates/eip7928/Cargo.toml
crates.iorand—crates/eip7928/Cargo.toml
crates.ioalloy-primitives—crates/eip8141/Cargo.toml
crates.ioalloy-rlp—crates/eip8141/Cargo.toml
crates.iothiserror—crates/eip8141/Cargo.toml
crates.ioserde—crates/eip8141/Cargo.toml
crates.ioborsh—crates/eip8141/Cargo.toml
crates.ioarbitrary—crates/eip8141/Cargo.toml
All dependencies 4

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

RegistryPackageVersionRelation
crates.iocrc—direct
crates.iorand—direct
crates.ioserde_with—direct
crates.iobincode—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 alloy-rs/eips. Read them side by side →

100scalar/scalarScalar is an open-source API platform:　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　🌐 Modern REST API Client　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　📖 Beautiful API References　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　✨ 1st-Class OpenAPI/Swagger SupportExceptional100envoyproxy/envoyCloud-native high-performance edge/middle/service proxyExceptional100risingwavelabs/risingwaveEvent streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.Exceptional100wandb/wandbThe AI developer platform. Use Weights & Biases to train and fine-tune models, and manage models from experimentation to production.Exceptional100microsoft/onnxruntimeONNX Runtime: cross-platform, high performance ML inferencing and training acceleratorExceptional99ai-dynamo/dynamoA Datacenter Scale Distributed Inference Serving FrameworkExceptional

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.