Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-25 23:02 UTC

Zondax / ledger-cosmos-js

TypeScriptApache-2.0★ 31 stars⑂ 69 forkssince Jul 2018View on GitHub ↗

Zondax/ledger-cosmos-js holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (72/100) and lowest on Community & Adoption (51/100). It was last updated 40 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

zondaxOrganization · verified domain
124 followers378 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/ledger-cosmos-js4.2.023,683940 days agoledgertypescripttendermintcosmos

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
18/36Push recency — last push 40 days ago
2.8/36Commit cadence — 4/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year6
human_commit_share0.73
days_since_last_push40
active_weeks_last_year4
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 40 days ago
12.6/27Release cadence — a release every ~164.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv4.2.0
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases164.1
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?

51Moderate · 17% of overall
How it's scored
24/60Stars — 31 stars
15.3/25Forks — 69 forks
0/15Watchers — 2 watchers
Inputs used
forks69
stars31
watchers2
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)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
58.3/80Monthly downloads — 23,683 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@zondax/ledger-cosmos-js
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads23,683
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?

71Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.5/22.5Commit distribution — top contributor authored 71% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.712
How it's scored
42/42Issue resolution — 100% of issues closed
22.1/30PR acceptance — 53/72 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 4/27 approved changesets -- score normalized to 1
Inputs used
merged_prs53
open_issues0
closed_issues14
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs19
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
20/20Verified domain
15.1/25Owner reach — 124 followers of Zondax
25/25Track record — 378 public repos, account ~8 yr old
Inputs used
followers124
owner_typeOrganization
is_verifiedyes
owner_loginZondax
public_repos378
account_age_days3,243

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 40 days ago
20/20Version history — 9 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@zondax/ledger-cosmos-js
ecosystemsnpm
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 6 out of 10 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicscosmos-sdk
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.5/2.5CI-Tests — 6 out of 10 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 4/27 approved changesets -- score normalized to 1
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
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
2/5SAST — SAST tool is not run on all commits -- score normalized to 4
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 19 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages47
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@zondax/ledger-cosmos-js@4.2.0 runtime dependency closure — what installing the published package pulls in — 47 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32.1/40Legible commit history — 44 of 73 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.603
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — .mise.toml
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 27 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files.mise.toml
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.27
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/7 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes8,313
source_files_sampled7
oversized_source_files0

Key facts

31GitHub stars
5contributors
6commits, last 12 months
40days since last push
16releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 69 ⇿
0Stars
69Forks
12Releases

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.

048121620242122018-122022-082026-04
Major 2Minor 0Patch 10

Each point covers 7 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-25 23:02 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests6 out of 10 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/27 approved changesets -- score normalized to 1
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
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4SASTSAST tool is not run on all commits -- score normalized to 4
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities19 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npm@noble/hashes^1.8.0package.json
npm@scure/base^1.2.6package.json
npm@zondax/ledger-js^2.1.0package.json
npmbuffer^6.0.3package.json
npmripemd160^2.0.2package.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

Dependency advisories 0

Installing npm:@zondax/ledger-cosmos-js@4.2.0 pulls in 47 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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 statistics — npm.