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

nimiq / trust-web3-provider

Web3 javascript wrapper provider for iOS and Android platforms.

TypeScript · SwiftNo license detected★ 0 stars⑂ 1 forksince Jan 2026forkView on GitHub ↗
KindMobile applicationhow this is determined

nimiq/trust-web3-provider holds a health index of 33 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (72/100) and lowest on Community & Adoption (1/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

NimiqOrganization · verified domain
141 followers105 public repossince Nov 2017

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

Metrics by category

Vitality

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

38Weak · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
9.7/36Commit cadence14/52 weeks with commits
13.9/18Commit volume34 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year34
human_commit_share0.99
days_since_last_push2
active_weeks_last_year14
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno 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?

1Critical · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
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?

50Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.5/22.5Commit distributiontop contributor authored 80% of commits
10.8/13.5Contributor breadth8 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.802
How it's scored
0/42Issue resolutionno issues or no data
18/30PR acceptance3/5 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/26 approved changesets -- score normalized to 1
Inputs used
merged_prs3
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d2
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
15.5/25Owner reach141 followers of nimiq
25/25Track record105 public repos, account ~8 yr old
Inputs used
followers141
owner_typeOrganization
is_verifiedyes
owner_loginnimiq
public_repos105
account_age_days3,224

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://trustwallet.com
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://trustwallet.com
docs_sitehttps://trustwallet.com
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

30At Risk · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 3 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
0.8/7.5Code-ReviewFound 3/26 approved changesets -- score normalized to 1
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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.5Vulnerabilities128 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3
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.

72Good · 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://trustwallet.com/llms.txt)
34.5/40Legible commit history64 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://trustwallet.com/llms.txt
legible_history_share0.646
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapandroid/app/build.gradle, android/build.gradle, android/lib/build.gradle (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingpackages/android-web3-provider/tsconfig.json, packages/aptos/tsconfig.json, packages/bitcoin/tsconfig.json, packages/core/tsconfig.json, packages/cosmos/tsconfig.json, packages/ethereum/tsconfig.json, packages/ios-web3-provider/tsconfig.json, packages/mini-app-sdk/tsconfig.json, packages/nimiq/tsconfig.json, packages/solana/tsconfig.json, packages/ton/tsconfig.json, packages/tron/tsconfig.json, templates/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance1 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
lockfilesbun.lockb, yarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/android-web3-provider/tsconfig.json, packages/aptos/tsconfig.json, packages/bitcoin/tsconfig.json, packages/core/tsconfig.json, packages/cosmos/tsconfig.json, packages/ethereum/tsconfig.json, packages/ios-web3-provider/tsconfig.json, packages/mini-app-sdk/tsconfig.json, packages/nimiq/tsconfig.json, packages/solana/tsconfig.json, packages/ton/tsconfig.json, packages/tron/tsconfig.json, templates/tsconfig.json, tsconfig.json
agent_commit_share0.01
toolchain_manifestsandroid/app/build.gradle, android/build.gradle, android/lib/build.gradle
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.6/55Manageable file sizes1/135 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes1,321,783
source_files_sampled135
oversized_source_files1

Key facts

0GitHub stars
8contributors
34commits, last 12 months
2days since last push
0releases
1bus factor
0open issues
Maven, npmpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • Could not fetch npm package '@trustwallet/web3-provider-{{camelCase name}}' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-ton' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-core' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-tron' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-aptos' from its registry
  • Could not fetch npm package '@nimiq/web3-provider-nimiq' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-cosmos' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-solana' from its registry
  • Could not fetch npm package '@trustwallet/web3-provider-bitcoin' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.0 / 10
3.0aggregate

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 10:48 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/26 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
0Vulnerabilities128 existing vulnerabilities detected
Direct dependencies 42
RegistryPackageVersion constraintManifest
npmsemantic-release-export-data^1.1.0package.json
npmsemantic-release^24.2.0package.json
npm@trustwallet/web3-provider-aptosworkspace:*packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-cosmosworkspace:*packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-ethereumworkspace:*packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-solanaworkspace:*packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-tonworkspace:*packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-bitcoinworkspace:*packages/android-web3-provider/package.json
npm@nimiq/web3-provider-nimiqworkspace:*packages/android-web3-provider/package.json
npmcore-js^3.38.1packages/android-web3-provider/package.json
npmuuid9.0.1packages/android-web3-provider/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/bitcoin/package.json
npm@wallet-standard/base1.1.0packages/bitcoin/package.json
npm@wallet-standard/features1.0.3packages/bitcoin/package.json
npmevents^3.3.0packages/core/package.json
npmuuid9.0.1packages/core/package.json
npm@cosmjs/amino0.32.3packages/cosmos/package.json
npm@cosmjs/proto-signing^0.32.3packages/cosmos/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/cosmos/package.json
npm@metamask/eth-sig-util^7.0.1packages/ethereum/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/ethereum/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/ios-web3-provider/package.json
npm@trustwallet/web3-provider-ethereumworkspace:*packages/ios-web3-provider/package.json
npm@trustwallet/web3-provider-solanaworkspace:*packages/ios-web3-provider/package.json
npm@trustwallet/web3-provider-cosmosworkspace:*packages/ios-web3-provider/package.json
npm@trustwallet/web3-provider-aptosworkspace:*packages/ios-web3-provider/package.json
npm@trustwallet/web3-provider-tonworkspace:*packages/ios-web3-provider/package.json
npm@trustwallet/web3-provider-bitcoinworkspace:*packages/ios-web3-provider/package.json
npm@nimiq/web3-provider-nimiqworkspace:*packages/ios-web3-provider/package.json
npmrollup-plugin-polyfill-node0.13.0packages/ios-web3-provider/package.json
npm@solana/wallet-standard-features1.2.0packages/solana/package.json
npm@solana/web3.js1.91.8packages/solana/package.json
npm@wallet-standard/base1.1.0packages/solana/package.json
npm@wallet-standard/features1.0.3packages/solana/package.json
npmbs584.0.1packages/solana/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/solana/package.json
npmrpc-websockets7.11.0packages/solana/package.json
npm@ton/crypto3.3.0packages/ton/package.json
npm@ton/ton15.1.0packages/ton/package.json
npm@trustwallet/web3-provider-coreworkspace:*packages/ton/package.json
npmtronweb6.0.1packages/tron/package.json
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

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.