Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 16:39 UTC

foundry-rs / foundry-toolchain

GitHub action to install Foundry

TypeScriptApache-2.0★ 275 stars⑂ 132 forkssince Jan 2022View on GitHub ↗

foundry-rs/foundry-toolchain holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Engineering Quality (45/100). It was last updated today. 2 contributors account 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

FoundryOrganization
1,540 followers27 public repossince Feb 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@foundry-rs/foundry-toolchain1.0.82921344 days agofoundryethereumsolidityevmforgecastdappdapptools

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
16.3/18Commit volume64 commits in the last year
10/10OpenSSF Scorecard: Maintained26 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year64
human_commit_share0.67
days_since_last_push0
active_weeks_last_year28
How it's scored
27/27Ships releases23 releases published
36/36Release recencylatest release 52 days ago
19.8/27Release cadencea release every ~97.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count23
latest_release_tagv1.9.1
releases_from_tagsno
days_since_latest_release52
mean_days_between_releases97.7
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?

56Moderate · 17% of overall
How it's scored
39.5/60Stars275 stars
17.6/25Forks132 forks
5/15Watchers9 watchers
Inputs used
forks132
stars275
watchers9
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

Sustainability & Governance

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

73Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
16.1/22.5Commit distributiontop contributor authored 29% of commits
13.5/13.5Contributor breadth12 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.286
How it's scored
41.1/42Issue resolution98% of issues closed
23.2/30PR acceptance95/123 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs95
open_issues1
closed_issues47
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.979
closed_unmerged_prs28
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 backingorganization-owned
0/20Verified domain
22.9/25Owner reach1,540 followers of foundry-rs
19.7/25Track record27 public repos, account ~4 yr old
Inputs used
followers1,540
owner_typeOrganization
is_verifiedno
owner_loginfoundry-rs
public_repos27
account_age_days1,675
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 1,344 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@foundry-rs/foundry-toolchain
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,344

Engineering Quality

Are baseline engineering and documentation practices in place?

45Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests28 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsfoundry, ethereum, dapptools, solidity, solidity-testing
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.2/2.5CI-Tests28 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 6 contributing companies or organizations
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained26 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
4.5/5SASTSAST tool detected but not run on all commits
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_aggregate6.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
5.6/25Indirect dependencies free of known advisories6 affected: undici 5.29.0 (high 7.5), uuid 3.4.0 (high 7.5), uuid 8.3.2 (high 7.5), +3 more
20.4/40No advisories left outstanding6 advisory-carrying package(s) unaddressed past 90 days; oldest published 581 days ago
Inputs used
sourceosv
advisories17
affected_packages6
assessed_packages100
unassessed_packages0
affected_by_severityhigh 3, moderate 3
direct_affected_packages0
Matched the npm:@foundry-rs/foundry-toolchain@1.0.8 runtime dependency closure — what installing the published package pulls in — 100 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.

66Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history65 of 67 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.97
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes768
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance33 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.33
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/3 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes4,993
source_files_sampled3
oversized_source_files0

Key facts

275GitHub stars
12contributors
64commits, last 12 months
0days since last push
23releases
2bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 132 ⇿
0Stars
132Forks
16Releases

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.

0255075100125125362022-022024-052026-07
Major 0Minor 9Patch 7

Each point covers 5 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-19 16:38 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests28 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 6 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained26 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool detected but not run on all commits
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npm@actions/cache6.1.0package.json
npm@actions/core3.0.1package.json
npm@actions/github9.1.1package.json
npm@actions/tool-cache4.0.0package.json
All dependencies 83

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

RegistryPackageVersionRelation
npm@actions/cache6.1.0direct
npm@actions/core3.0.1direct
npm@actions/github9.1.1direct
npm@actions/tool-cache4.0.0direct
npm@actions/exec3.0.0indirect
npm@actions/glob0.6.1indirect
npm@actions/http-client3.0.2indirect
npm@actions/http-client4.0.1indirect
npm@actions/io3.0.2indirect
npm@azure/abort-controller2.1.2indirect
npm@azure/core-auth1.10.1indirect
npm@azure/core-client1.10.1indirect
npm@azure/core-http-compat2.4.0indirect
npm@azure/core-lro2.7.2indirect
npm@azure/core-paging1.6.2indirect
npm@azure/core-rest-pipeline1.23.0indirect
npm@azure/core-tracing1.3.1indirect
npm@azure/core-util1.13.1indirect
npm@azure/core-xml1.5.1indirect
npm@azure/logger1.3.0indirect
npm@azure/storage-blob12.31.0indirect
npm@azure/storage-common12.3.0indirect
npm@nodable/entities2.2.0indirect
npm@octokit/auth-token6.0.0indirect
npm@octokit/core7.0.6indirect
npm@octokit/endpoint11.0.3indirect
npm@octokit/graphql9.0.3indirect
npm@octokit/openapi-types27.0.0indirect
npm@octokit/plugin-paginate-rest14.0.0indirect
npm@octokit/plugin-rest-endpoint-methods17.0.0indirect
npm@octokit/request10.0.8indirect
npm@octokit/request-error7.1.0indirect
npm@octokit/types16.0.0indirect
npm@protobuf-ts/runtime2.11.1indirect
npm@protobuf-ts/runtime-rpc2.11.1indirect
npm@types/node26.4.1indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npm@typespec/ts-http-runtime0.3.5indirect
npm@vercel/ncc0.45.0indirect
npmagent-base7.1.4indirect
npmbalanced-match1.0.2indirect
npmbefore-after-hook4.0.0indirect
npmbrace-expansion1.1.18indirect
npmconcat-map0.0.1indirect
npmdebug4.4.3indirect
npmevents3.3.0indirect
npmfast-content-type-parse3.0.0indirect
npmfast-xml-builder1.1.7indirect
npmfast-xml-parser5.7.0indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmjson-with-bigint3.5.8indirect
npmminimatch3.1.5indirect
npmms2.1.3indirect
npmpath-expression-matcher1.5.0indirect
npmprettier3.9.6indirect
npmsemver7.7.4indirect
npmstrnum2.2.3indirect
npmtslib2.8.1indirect
npmtunnel0.0.6indirect
npmtypescript7.0.2indirect
npmundici6.28.1indirect
npmundici-types8.3.0indirect
npmuniversal-user-agent7.0.3indirect
Dependency advisories 6

Installing npm:@foundry-rs/foundry-toolchain@1.0.8 pulls in 100 packages, direct and transitive: 6 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
undici5.29.0indirecthigh128.9.0
uuid3.4.0indirecthigh113.0.1
uuid8.3.2indirecthigh113.0.1
@octokit/plugin-paginate-rest2.21.3indirectmoderate111.4.1
@octokit/request5.6.3indirectmoderate19.2.1
@octokit/request-error2.1.0indirectmoderate16.1.7

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

How one result sits in the wider record: aggregate statisticsnpm.