Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 20:00 UTC

Zondax / filecoin-solidity

Filecoin Solidity API Library

Solidity · RustApache-2.0★ 97 stars⑂ 44 forkssince Nov 2022archivedView on GitHub ↗

Zondax/filecoin-solidity holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (69/100) and lowest on Vitality (25/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 49 is calibrated to 48 on the published index scale (record calibration 2026-08-02).

Ownership

zondaxOrganization · verified domain
122 followers375 public repossince Dec 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@zondax/filecoin-solidity4.0.3540131251 days agofevmevmsolidityfilecoin
crates.iotestingpoints to another repo — not scored27.0.0307,74021036 days ago

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 1,117 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year0
human_commit_share0.96
days_since_last_push1,117
active_weeks_last_year0
How it's scored
27/27Ships releases21 releases published
0/36Release recencylatest release 1,251 days ago
27/27Release cadencea release every ~9.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tagv4.0.3
releases_from_tagsno
days_since_latest_release1,251
mean_days_between_releases9.9
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?

47Weak · 17% of overall
How it's scored
32.2/60Stars97 stars
13.6/25Forks44 forks
0/15Watchers2 watchers
Inputs used
forks44
stars97
watchers2
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
36.4/80Monthly downloads540 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@zondax/filecoin-solidity
dependents
ecosystemsnpm
total_downloads
monthly_downloads540
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
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.2/22.5Commit distributiontop contributor authored 68% of commits
13.5/13.5Contributor breadth15 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.68
How it's scored
39.3/42Issue resolution94% of issues closed
26.9/30PR acceptance201/224 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 9/28 approved changesets -- score normalized to 3
Inputs used
merged_prs201
open_issues10
closed_issues147
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.936
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.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
15/25Owner reach122 followers of Zondax
25/25Track record375 public repos, account ~8 yr old
Inputs used
followers122
owner_typeOrganization
is_verifiedyes
owner_loginZondax
public_repos375
account_age_days3,207
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 1,251 days ago
20/20Version history13 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@zondax/filecoin-solidity
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,251

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 27 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
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsapi, evm, fevm, filecoin, smart-contracts, solidity, blockchain
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 27 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 9/28 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject is archived
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities202 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
2/25Indirect dependencies free of known advisories17 affected: decode-uri-component 0.2.2 (high 7.5), elliptic 6.5.4 (high 7.5), elliptic 6.6.1 (high 7.3), +14 more
10.8/40No advisories left outstanding16 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,206 days ago
Inputs used
sourceosv
advisories39
affected_packages17
assessed_packages561
unassessed_packages0
affected_by_severityhigh 10, moderate 7
direct_affected_packages0
Matched the npm:@zondax/filecoin-solidity@4.0.3 runtime dependency closure — what installing the published package pulls in — 561 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.

63Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.filecoin.io/llms.txt)
40/40Legible commit history89 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.filecoin.io/llms.txt
legible_history_share0.927
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, yarn.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifeststesting/Cargo.toml
dependency_bot_commit_share0.04
How it's scored
0/45Type-checkable codeSolidity without a type-check config
55/55Manageable file sizes0/33 source files over 60KB
Inputs used
primary_languageSolidity
largest_source_bytes33,868
source_files_sampled33
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

97GitHub stars
15contributors
0commits, last 12 months
1,117days since last push
21releases
1bus factor
10open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'testing' points at a different repository (https://github.com/swc-project/swc.git); excluded from ecosystem scoring
  • Could not fetch npm package 'FVM-Hardhat-Kit' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 44 ⇿
0Stars
44Forks
21Releases

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.

010203040504332022-122024-022025-04
Major 1Minor 0Patch 3

Each point covers 3 days.

OpenSSF Scorecard 3.8 / 10
3.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 20:00 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 27 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 9/28 approved changesets -- score normalized to 3
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities202 existing vulnerabilities detected
Direct dependencies 38
RegistryPackageVersion constraintManifest
npm@glif/filecoin-address^2.0.18hardhat/package.json
npm@nomicfoundation/hardhat-chai-matchers^1.0.5hardhat/package.json
npm@nomicfoundation/hardhat-network-helpers^1.0.0hardhat/package.json
npm@nomicfoundation/hardhat-toolbox^2.0.0hardhat/package.json
npm@openzeppelin/contracts^4.8.3hardhat/package.json
npm@typechain/hardhat^6.1.2hardhat/package.json
npmbabel-eslint^10.1.0hardhat/package.json
npmdotenv^10.0.0hardhat/package.json
npmhardhat-deploy-ethers^0.3.0-beta.13hardhat/package.json
npmts-node>=8.0.0hardhat/package.json
npmtypescript>=4.5.0hardhat/package.json
npmsolidity-cborutils^2.0.0package.json
npm@zondax/solidity-bignumber^0.1.0package.json
crates.iofvm_ipld_blockstore0.1.1testing/Cargo.toml
crates.iofvm_shared3.0.0-alpha.17testing/Cargo.toml
crates.iofvm3.0.0-alpha.21testing/Cargo.toml
crates.iofvm_ipld_encoding0.3.3testing/Cargo.toml
crates.iofvm_integration_tests3.0.0-alpha.1testing/Cargo.toml
crates.ioserde1.0testing/Cargo.toml
crates.ioserde_tuple0.5testing/Cargo.toml
crates.iowabt0.10.0testing/Cargo.toml
crates.iohex0.4.3testing/Cargo.toml
crates.iobls-signatures0.13.0testing/Cargo.toml
crates.iomultihash0.16.1testing/Cargo.toml
crates.iolibipld-core0.13.1testing/Cargo.toml
crates.iocid0.8.6testing/Cargo.toml
crates.iorand_core0.6.4testing/Cargo.toml
crates.ioanyhow1.0.47testing/Cargo.toml
crates.ioprettytable-rs0.10testing/Cargo.toml
crates.iofil_actors_runtime10.0.0-alpha.1testing/Cargo.toml
crates.iofil_actor_eam10.0.0-alpha.1testing/Cargo.toml
crates.iofil_actor_datacap10.0.0-alpha.1testing/Cargo.toml
crates.iofil_actor_init10.0.0-alpha.1testing/Cargo.toml
crates.iofil_actor_miner10.0.0-alpha.1testing/Cargo.toml
crates.iofil_actor_evm10.0.0-alpha.1testing/Cargo.toml
crates.iofvm_actor_utils4.0.0testing/Cargo.toml
crates.iofrc46_token4.0.0testing/Cargo.toml
crates.iofrc42_dispatch3.0.1-alpha.1testing/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

Dependency advisories 17

Installing npm:@zondax/filecoin-solidity@4.0.3 pulls in 561 packages, direct and transitive: 17 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
decode-uri-component0.2.2indirecthigh10.5.0
elliptic6.5.4indirecthigh76.6.1
elliptic6.6.1indirecthigh1
form-data2.3.3indirecthigh24.0.6
tar4.4.19indirecthigh137.5.21
uuid2.0.1indirecthigh113.0.1
uuid3.4.0indirecthigh113.0.1
uuid9.0.1indirecthigh113.0.1
ws3.3.3indirecthigh28.21.0
ws8.18.0indirecthigh28.21.0
bn.js4.11.6indirectmoderate15.2.3
qs6.5.5indirectmoderate26.16.0
request2.88.2indirectmoderate13.0.0
tough-cookie2.5.0indirectmoderate14.1.3
web3-core-method1.10.0indirectmoderate1
web3-core-subscriptions1.10.0indirectmoderate1
yargs-parser2.4.1indirectmoderate118.1.1

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, crates.io.