Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 16:05 UTC

dawsbot / satoshi-bitcoin

Convert precisely between Satoshi and Bitcoin

JavaScriptMIT★ 42 stars⑂ 6 forkssince Jul 2015View on GitHub ↗

dawsbot/satoshi-bitcoin holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (63/100) and lowest on AI Readiness (45/100). It was last updated 41 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Dawson BotsfordPersonal account
1,194 followers100 public repossince Jan 2013

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

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

45Weak · 21% of overall
How it's scored
18/36Push recency — last push 41 days ago
1.4/36Commit cadence — 2/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year6
human_commit_share0.988
days_since_last_push41
active_weeks_last_year2
How it's scored
16.2/27Ships releases — 14 version tags (no GitHub releases)
36/36Release recency — latest release 68 days ago
5.4/27Release cadence — a release every ~420.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv1.0.6
releases_from_tagsyes
days_since_latest_release68
mean_days_between_releases420.2
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?

48Weak · 17% of overall
How it's scored
26.2/60Stars — 42 stars
5.8/25Forks — 6 forks
0/15Watchers — 2 watchers
Inputs used
forks6
stars42
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
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
55.6/80Monthly downloads — 14,800 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessatoshi-bitcoin
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads14,800
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.9/22.5Commit distribution — top contributor authored 92% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.915
How it's scored
36/42Issue resolution — 86% of issues closed
15.5/30PR acceptance — 16/31 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 4/25 approved changesets -- score normalized to 1
Inputs used
merged_prs16
open_issues1
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.857
closed_unmerged_prs15
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
22.1/25Owner reach — 1,194 followers of dawsbot
25/25Track record — 100 public repos, account ~13 yr old
Inputs used
followers1,194
owner_typeUser
is_verified—
owner_logindawsbot
public_repos100
account_age_days4,977
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 41 days ago
20/20Version history — 16 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessatoshi-bitcoin
ecosystemsnpm
any_deprecatedno
min_days_since_publish41

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 5 out of 12 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsbitcoin, crypto, satoshi
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?

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1/2.5CI-Tests — 5 out of 12 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 4/25 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 4 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
3.8/7.5Maintained — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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 — 33 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
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_packages1
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:satoshi-bitcoin@1.0.7 runtime dependency closure — what installing the published package pulls in — 1 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14.3/40Legible commit history — 22 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.268
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 5 of the last 83 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 83 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.012
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/4 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes18,314
source_files_sampled4
oversized_source_files0

Key facts

42GitHub stars
2contributors
6commits, last 12 months
41days since last push
14releases
1bus 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 ★ / 6 ⇿
0Stars
6Forks
2Releases

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.

123456612016-042019-062022-09
Major 0Minor 0Patch 2

Each point covers 6 days.

OpenSSF Scorecard 4.0 / 10
4.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-15 16:05 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests5 out of 12 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/25 approved changesets -- score normalized to 1
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
0Vulnerabilities33 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmbig.js^3.1.3package.json
All dependencies 177

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

RegistryPackageVersionRelation
npmbig.js3.2.0direct
npm@esbuild/aix-ppc640.28.1indirect
npm@esbuild/android-arm0.28.1indirect
npm@esbuild/android-arm640.28.1indirect
npm@esbuild/android-x640.28.1indirect
npm@esbuild/darwin-arm640.28.1indirect
npm@esbuild/darwin-x640.28.1indirect
npm@esbuild/freebsd-arm640.28.1indirect
npm@esbuild/freebsd-x640.28.1indirect
npm@esbuild/linux-arm0.28.1indirect
npm@esbuild/linux-arm640.28.1indirect
npm@esbuild/linux-ia320.28.1indirect
npm@esbuild/linux-loong640.28.1indirect
npm@esbuild/linux-mips64el0.28.1indirect
npm@esbuild/linux-ppc640.28.1indirect
npm@esbuild/linux-riscv640.28.1indirect
npm@esbuild/linux-s390x0.28.1indirect
npm@esbuild/linux-x640.28.1indirect
npm@esbuild/netbsd-arm640.28.1indirect
npm@esbuild/netbsd-x640.28.1indirect
npm@esbuild/openbsd-arm640.28.1indirect
npm@esbuild/openbsd-x640.28.1indirect
npm@esbuild/openharmony-arm640.28.1indirect
npm@esbuild/sunos-x640.28.1indirect
npm@esbuild/win32-arm640.28.1indirect
npm@esbuild/win32-ia320.28.1indirect
npm@esbuild/win32-x640.28.1indirect
npmacorn3.3.0indirect
npmacorn5.7.4indirect
npmacorn-jsx3.0.1indirect
npmajv4.11.8indirect
npmajv-keywords1.5.1indirect
npmansi-escapes1.4.0indirect
npmansi-regex2.1.1indirect
npmansi-regex3.0.0indirect
npmansi-styles2.2.1indirect
npmargparse1.0.10indirect
npmassertion-error1.1.0indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmbuffer-from1.1.1indirect
npmcaller-path0.1.0indirect
npmcallsites0.2.0indirect
npmchai3.5.0indirect
npmchalk1.1.3indirect
npmcircular-json0.3.3indirect
npmcli-cursor1.0.2indirect
npmcli-width2.2.1indirect
npmco4.6.0indirect
npmcode-point-at1.1.0indirect
npmcommander0.6.1indirect
npmcommander2.3.0indirect
npmconcat-map0.0.1indirect
npmconcat-stream1.6.2indirect
npmcore-util-is1.0.2indirect
npmd1.0.1indirect
npmdebug2.2.0indirect
npmdebug2.6.9indirect
npmdeep-eql0.1.3indirect
npmdeep-is0.1.3indirect
npmdiff1.4.0indirect
npmdoctrine1.5.0indirect
npmes5-ext0.10.53indirect
npmes6-iterator2.0.3indirect
npmes6-map0.1.5indirect
npmes6-set0.1.5indirect
npmes6-symbol3.1.1indirect
npmes6-symbol3.1.3indirect
npmes6-weak-map2.0.3indirect
npmesbuild0.28.1indirect
npmescape-string-regexp1.0.2indirect
npmescape-string-regexp1.0.5indirect
npmescope3.6.0indirect
npmeslint2.13.1indirect
npmespree3.5.4indirect
npmesprima4.0.1indirect
npmesrecurse4.3.0indirect
npmestraverse4.3.0indirect
npmestraverse5.2.0indirect
npmesutils2.0.3indirect
npmevent-emitter0.3.5indirect
npmexit-hook1.1.1indirect
npmext1.4.0indirect
npmfast-levenshtein2.0.6indirect
npmfigures1.7.0indirect
npmfile-entry-cache1.3.1indirect
npmflat-cache1.3.4indirect
npmfs.realpath1.0.0indirect
npmgenerate-function2.3.1indirect
npmgenerate-object-property1.2.0indirect
npmglob3.2.11indirect
npmglob7.1.7indirect
npmglobals9.18.0indirect
npmgraceful-fs4.2.6indirect
npmgrowl1.9.2indirect
npmhas-ansi2.0.0indirect
npmignore3.3.10indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npminquirer0.12.0indirect
npmis-fullwidth-code-point1.0.0indirect
npmis-fullwidth-code-point2.0.0indirect
npmis-my-ip-valid1.0.0indirect
npmis-my-json-valid2.20.5indirect
npmis-property1.0.2indirect
npmis-resolvable1.1.0indirect
npmisarray1.0.0indirect
npmjade0.26.3indirect
npmjs-yaml3.14.1indirect
npmjson-stable-stringify1.0.1indirect
npmjsonify0.0.0indirect
npmjsonpointer4.1.0indirect
npmlevn0.3.0indirect
npmlodash4.17.21indirect
npmlru-cache2.7.3indirect
npmminimatch0.3.0indirect
npmminimatch3.0.4indirect
npmminimist0.0.8indirect
npmminimist1.2.5indirect
npmmkdirp0.3.0indirect
npmmkdirp0.5.1indirect
npmmkdirp0.5.5indirect
npmmocha2.5.3indirect
npmms0.7.1indirect
npmms2.0.0indirect
npmmute-stream0.0.5indirect
npmnext-tick1.0.0indirect
npmnumber-is-nan1.0.1indirect
npmobject-assign4.1.1indirect
npmonce1.4.0indirect
npmonetime1.1.0indirect
npmoptionator0.8.3indirect
npmos-homedir1.0.2indirect
npmpath-is-absolute1.0.1indirect
npmpath-is-inside1.0.2indirect
npmpluralize1.2.1indirect
npmprelude-ls1.1.2indirect
npmprocess-nextick-args2.0.1indirect
npmprogress1.1.8indirect
npmreadable-stream2.3.7indirect
npmreadline21.0.1indirect
npmrequire-uncached1.0.3indirect
npmresolve-from1.0.1indirect
npmrestore-cursor1.0.1indirect
npmrimraf2.6.3indirect
npmrun-async0.1.0indirect
npmrx-lite3.1.2indirect
npmsafe-buffer5.1.2indirect
npmshelljs0.6.1indirect
npmsigmund1.0.1indirect
npmslice-ansi0.0.4indirect
npmsprintf-js1.0.3indirect
npmstring-width1.0.2indirect
npmstring-width2.1.1indirect
npmstring_decoder1.1.1indirect
npmstrip-ansi3.0.1indirect
npmstrip-ansi4.0.0indirect
npmstrip-json-comments1.0.4indirect
npmsupports-color1.2.0indirect
npmsupports-color2.0.0indirect
npmtable3.8.3indirect
npmtext-table0.2.0indirect
npmthrough2.3.8indirect
npmto-iso-string0.0.2indirect
npmtype1.2.0indirect
npmtype2.5.0indirect
npmtype-check0.3.2indirect
npmtype-detect0.1.1indirect
npmtype-detect1.0.0indirect
npmtypedarray0.0.6indirect
npmuser-home2.0.0indirect
npmutil-deprecate1.0.2indirect
npmword-wrap1.2.3indirect
npmwrappy1.0.2indirect
npmwrite0.2.1indirect
npmxtend4.0.2indirect
Dependency advisories 0

Installing npm:satoshi-bitcoin@1.0.7 pulls in 1 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.