Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 16:38 UTC

indutny / proof-of-work

Proof of Work with SHA256 and Bloom filter

JavaScriptNo license detected★ 133 stars⑂ 20 forkssince May 2016View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

indutny/proof-of-work holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (56/100) and lowest on Vitality (20/100). It was last updated 2205 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Fedor IndutnyPersonal account
3,649 followers400 public repossince Apr 2010@signalapp

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmproof-of-work3.3.29,565263006 days agoproofofworksha256bloom

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
0/36Push recency — last push 2,205 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push2,205
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 27 version tags (no GitHub releases)
0/36Release recency — latest release 3,006 days ago
27/27Release cadence — a release every ~44.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count27
latest_release_tagv3.3.2
releases_from_tagsyes
days_since_latest_release3,006
mean_days_between_releases44.6
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?

44Weak · 17% of overall
How it's scored
34.4/60Stars — 133 stars
10.7/25Forks — 20 forks
3.3/15Watchers — 5 watchers
Inputs used
forks20
stars133
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, travis-ci.org
has_pull_request_templateno
How it's scored
53.1/80Monthly downloads — 9,565 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesproof-of-work
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads9,565
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.4/22.5Commit distribution — top contributor authored 98% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.984
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 1/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
25/25Owner reach — 3,649 followers of indutny
25/25Track record — 400 public repos, account ~16 yr old
Inputs used
followers3,649
owner_typeUser
is_verified—
owner_loginindutny
public_repos400
account_age_days6,038
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 3,006 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesproof-of-work
ecosystemsnpm
any_deprecatedno
min_days_since_publish3,006

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicsbloom-filter
has_wikiyes
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?

31At Risk · 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
0/2.5CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Vulnerabilities — 40 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages3
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:proof-of-work@3.3.2 runtime dependency closure — what installing the published package pulls in — 3 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29.6/40Legible commit history — 35 of 63 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.556
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 63
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
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
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/14 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes3,093
source_files_sampled14
oversized_source_files0

Key facts

133GitHub stars
2contributors
0commits, last 12 months
2,205days since last push
27releases
1bus factor
0open 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 ★ / 20 ⇿
0Stars
20Forks
4Releases

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.

0481216202012017-072020-022022-10
Major 0Minor 2Patch 2

Each point covers 5 days.

OpenSSF Scorecard 1.4 / 10
1.4aggregate

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-18 16:38 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities40 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmhash.js^1.1.5package.json
npmminimalistic-assert^1.0.1package.json
All dependencies 151

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

RegistryPackageVersionRelation
npmhash.js1.1.5direct
npmminimalistic-assert1.0.1direct
npmacorn3.3.0indirect
npmacorn5.7.1indirect
npmacorn-jsx3.0.1indirect
npmajv5.5.2indirect
npmajv-keywords2.1.1indirect
npmansi-escapes3.1.0indirect
npmansi-regex2.1.1indirect
npmansi-regex3.0.0indirect
npmansi-styles2.2.1indirect
npmansi-styles3.2.1indirect
npmargparse1.0.10indirect
npmarray-union1.0.2indirect
npmarray-uniq1.0.3indirect
npmarrify1.0.1indirect
npmbabel-code-frame6.26.0indirect
npmbalanced-match1.0.0indirect
npmbenchmark2.1.4indirect
npmbrace-expansion1.1.11indirect
npmbrowser-stdout1.3.1indirect
npmbuffer-from1.1.0indirect
npmcaller-path0.1.0indirect
npmcallsites0.2.0indirect
npmchalk1.1.3indirect
npmchalk2.4.1indirect
npmchardet0.4.2indirect
npmcircular-json0.3.3indirect
npmcli-cursor2.1.0indirect
npmcli-width2.2.0indirect
npmco4.6.0indirect
npmcolor-convert1.9.2indirect
npmcolor-name1.1.1indirect
npmcommander2.15.1indirect
npmconcat-map0.0.1indirect
npmconcat-stream1.6.2indirect
npmcore-util-is1.0.2indirect
npmcross-spawn5.1.0indirect
npmdebug3.1.0indirect
npmdeep-is0.1.3indirect
npmdel2.2.2indirect
npmdiff3.5.0indirect
npmdoctrine2.1.0indirect
npmescape-string-regexp1.0.5indirect
npmeslint4.19.1indirect
npmeslint-scope3.7.3indirect
npmeslint-visitor-keys1.0.0indirect
npmespree3.5.4indirect
npmesprima4.0.1indirect
npmesquery1.0.1indirect
npmesrecurse4.2.1indirect
npmestraverse4.2.0indirect
npmesutils2.0.2indirect
npmexternal-editor2.2.0indirect
npmfast-deep-equal1.1.0indirect
npmfast-json-stable-stringify2.0.0indirect
npmfast-levenshtein2.0.6indirect
npmfigures2.0.0indirect
npmfile-entry-cache2.0.0indirect
npmflat-cache1.3.0indirect
npmfs.realpath1.0.0indirect
npmfunctional-red-black-tree1.0.1indirect
npmglob7.1.2indirect
npmglobals11.7.0indirect
npmglobby5.0.0indirect
npmgraceful-fs4.1.11indirect
npmgrowl1.10.5indirect
npmhas-ansi2.0.0indirect
npmhas-flag3.0.0indirect
npmhe1.1.1indirect
npmiconv-lite0.4.23indirect
npmignore3.3.10indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.3indirect
npminquirer3.3.0indirect
npmis-fullwidth-code-point2.0.0indirect
npmis-path-cwd1.0.0indirect
npmis-path-in-cwd1.0.1indirect
npmis-path-inside1.0.1indirect
npmis-promise2.1.0indirect
npmis-resolvable1.1.0indirect
npmisarray1.0.0indirect
npmisexe2.0.0indirect
npmjs-tokens3.0.2indirect
npmjs-yaml3.12.0indirect
npmjson-schema-traverse0.3.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmlevn0.3.0indirect
npmlodash4.17.10indirect
npmlru-cache4.1.3indirect
npmmimic-fn1.2.0indirect
npmminimatch3.0.4indirect
npmminimist0.0.8indirect
npmmkdirp0.5.1indirect
npmmocha5.2.0indirect
npmms2.0.0indirect
npmmute-stream0.0.7indirect
npmnatural-compare1.4.0indirect
npmobject-assign4.1.1indirect
npmonce1.4.0indirect
npmonetime2.0.1indirect
npmoptionator0.8.2indirect
npmos-tmpdir1.0.2indirect
npmpath-is-absolute1.0.1indirect
npmpath-is-inside1.0.2indirect
npmpify2.3.0indirect
npmpinkie2.0.4indirect
npmpinkie-promise2.0.1indirect
npmplatform1.3.4indirect
npmpluralize7.0.0indirect
npmprelude-ls1.1.2indirect
npmprocess-nextick-args2.0.0indirect
npmprogress2.0.0indirect
npmpseudomap1.0.2indirect
npmreadable-stream2.3.6indirect
npmregexpp1.1.0indirect
npmrequire-uncached1.0.3indirect
npmresolve-from1.0.1indirect
npmrestore-cursor2.0.0indirect
npmrimraf2.6.2indirect
npmrun-async2.3.0indirect
npmrx-lite4.0.8indirect
npmrx-lite-aggregates4.0.8indirect
npmsafe-buffer5.1.2indirect
npmsafer-buffer2.1.2indirect
npmsemver5.5.0indirect
npmshebang-command1.2.0indirect
npmshebang-regex1.0.0indirect
npmsignal-exit3.0.2indirect
npmslice-ansi1.0.0indirect
npmsprintf-js1.0.3indirect
npmstring-width2.1.1indirect
npmstring_decoder1.1.1indirect
npmstrip-ansi3.0.1indirect
npmstrip-ansi4.0.0indirect
npmstrip-json-comments2.0.1indirect
npmsupports-color2.0.0indirect
npmsupports-color5.4.0indirect
npmtable4.0.2indirect
npmtext-table0.2.0indirect
npmthrough2.3.8indirect
npmtmp0.0.33indirect
npmtype-check0.3.2indirect
npmtypedarray0.0.6indirect
npmutil-deprecate1.0.2indirect
npmwhich1.3.1indirect
npmwordwrap1.0.0indirect
npmwrappy1.0.2indirect
npmwrite0.2.1indirect
npmyallist2.1.2indirect
Dependency advisories 0

Installing npm:proof-of-work@3.3.2 pulls in 3 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.