Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 23:54 UTC

handshake-org / hsd

Handshake Daemon & Full Node

JavaScriptCustom license★ 2,069 stars⑂ 305 forkssince Mar 2018View on GitHub ↗

handshake-org/hsd holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (70/100) and lowest on AI Readiness (28/100). It was last updated 327 days ago. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

HandshakeOrganization
413 followers24 public repossince Jun 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmhsd8.0.01,48924379 days agoblockchaincryptocurrencyhandshakehnswallet

Metrics by category

Vitality

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

33At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 327 days ago
2.8/36Commit cadence4/52 weeks with commits
8.1/18Commit volume7 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year7
human_commit_share
days_since_last_push327
active_weeks_last_year4
How it's scored
27/27Ships releases22 releases published
7.2/36Release recencylatest release 379 days ago
19.8/27Release cadencea release every ~79.3 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count22
latest_release_tagv8.0.0
releases_from_tagsno
days_since_latest_release379
mean_days_between_releases79.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

70Good · 17% of overall
How it's scored
53.8/60Stars2,069 stars
20.7/25Forks305 forks
10.6/15Watchers81 watchers
Inputs used
forks305
stars2,069
watchers81
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
42.3/80Monthly downloads1,489 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageshsd
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,489
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.9/22.5Commit distributiontop contributor authored 78% of commits
13.5/13.5Contributor breadth56 contributors
10/10OpenSSF Scorecard: Contributorsproject has 31 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled56
top_contributor_share0.781
How it's scored
30.2/42Issue resolution72% of issues closed
20.7/30PR acceptance407/589 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 3/12 approved changesets -- score normalized to 2
Inputs used
merged_prs407
open_issues97
closed_issues250
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.72
closed_unmerged_prs182
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18.8/25Owner reach413 followers of handshake-org
22.2/25Track record24 public repos, account ~9 yr old
Inputs used
followers413
owner_typeOrganization
is_verified
owner_loginhandshake-org
public_repos24
account_age_days3,308
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
14/35Publish recencylatest publish 379 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageshsd
ecosystemsnpm
any_deprecatedno
min_days_since_publish379

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
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?

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 3/12 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 31 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packagingpackaging workflow detected
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
5/5Security-Policysecurity policy file detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection. 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.

28At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
52.8/55Manageable file sizes12/302 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes141,122
source_files_sampled302
oversized_source_files12

Key facts

2,069GitHub stars
56contributors
7commits, last 12 months
327days since last push
22releases
1bus factor
97open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.0 / 10
5.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-07-15 23:53 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
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 3/12 approved changesets -- score normalized to 2
10Contributorsproject has 31 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
npmbfilter~2.4.0package.json
npmbcfg~0.2.2package.json
npmbcrypto~5.5.2package.json
npmbcurl~0.2.1package.json
npmbdb~1.6.2package.json
npmbdns~0.1.5package.json
npmbevent~0.1.6package.json
npmbfile~0.2.3package.json
npmbheep~0.1.6package.json
npmbinet~0.3.9package.json
npmblgr~0.2.1package.json
npmblru~0.1.8package.json
npmblst~0.1.6package.json
npmbmutex~0.1.8package.json
npmbns~0.16.0package.json
npmbsert~0.0.13package.json
npmbsock~0.1.11package.json
npmbsocks~0.2.6package.json
npmbtcp~0.1.5package.json
npmbuffer-map~0.0.8package.json
npmbufio~1.2.3package.json
npmbupnp~0.2.6package.json
npmbval~0.1.8package.json
npmbweb~0.3.0package.json
npmgoosig~0.11.0package.json
npmn64~0.2.10package.json
npmurkel~1.0.3package.json
All dependencies 35

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

RegistryPackageVersionRelation
npmbcfg0.2.2direct
npmbcrypto5.5.2direct
npmbcurl0.2.1direct
npmbdb1.6.2direct
npmbdns0.1.5direct
npmbevent0.1.6direct
npmbfile0.2.3direct
npmbfilter2.4.0direct
npmbheep0.1.6direct
npmbinet0.3.9direct
npmblgr0.2.1direct
npmblru0.1.8direct
npmblst0.1.6direct
npmbmutex0.1.8direct
npmbns0.16.0direct
npmbsert0.0.13direct
npmbsock0.1.11direct
npmbsocks0.2.6direct
npmbtcp0.1.5direct
npmbuffer-map0.0.8direct
npmbufio1.0.7direct
npmbufio1.2.3direct
npmbupnp0.2.6direct
npmbval0.1.8direct
npmbweb0.3.0direct
npmgoosig0.11.0direct
npmn640.2.10direct
npmurkel1.0.3direct
npmbmocha2.2.1indirect
npmbrq0.1.10indirect
npmbs320.1.7indirect
npmbslintrc0.0.3indirect
npmbudp0.1.6indirect
npmloady0.0.5indirect
npmunbound0.4.3indirect
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.11.0 — full methodology · metrics wiki.

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