Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 12:46 UTC

ChetanXpro / nodejs-whisper

NodeJS Bindings for Whisper - the CPU version of OpenAI's Whisper, as initially crafted in C++ by ggerganov.

TypeScript · JavaScriptMIT★ 211 stars⑂ 43 forkssince Jul 2023View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ChetanXpro/nodejs-whisper holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (64/100) and lowest on Security (52/100). It was last updated 42 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ChetanPersonal account
131 followers125 public repossince Jun 2022

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?

53Moderate · 21% of overall
How it's scored
18/36Push recency — last push 42 days ago
1.4/36Commit cadence — 2/52 weeks with commits
9/18Commit volume — 9 commits in the last year
4/10OpenSSF Scorecard: Maintained — 4 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year9
human_commit_share0.7
days_since_last_push42
active_weeks_last_year2
How it's scored
27/27Ships releases — 8 releases published
36/36Release recency — latest release 43 days ago
12.6/27Release cadence — a release every ~157 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count8
latest_release_tagv0.3.1
releases_from_tagsno
days_since_latest_release43
mean_days_between_releases157
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?

58Moderate · 17% of overall
How it's scored
37.7/60Stars — 211 stars
13.5/25Forks — 43 forks
1.7/15Watchers — 3 watchers
Inputs used
forks43
stars211
watchers3
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
62.2/80Monthly downloads — 45,995 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnodejs-whisper
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads45,995
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.7/22.5Commit distribution — top contributor authored 92% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.924
How it's scored
33.1/42Issue resolution — 79% of issues closed
21.1/30PR acceptance — 147/209 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/16 approved changesets -- score normalized to 1
Inputs used
merged_prs147
open_issues11
closed_issues41
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.788
closed_unmerged_prs62
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
15.2/25Owner reach — 131 followers of ChetanXpro
21.5/25Track record — 125 public repos, account ~4 yr old
Inputs used
followers131
owner_typeUser
is_verified—
owner_loginChetanXpro
public_repos125
account_age_days1,549
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 43 days ago
20/20Version history — 41 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnodejs-whisper
ecosystemsnpm
any_deprecatedno
min_days_since_publish43

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 6 out of 26 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://npmjs.com/nodejs-whisper
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsopenai, speech-recognition, speech-to-text, timestamp, whisper, whisper-nodejs, nodejs-whisper, ai, cpp, ml
has_wikiyes
homepagehttps://npmjs.com/nodejs-whisper
docs_sitehttps://npmjs.com/nodejs-whisper
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
0.5/2.5CI-Tests — 6 out of 26 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/16 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 6 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/7.5Maintained — 4 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
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 — 13 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_packages36
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:nodejs-whisper@0.3.1 runtime dependency closure — what installing the published package pulls in — 36 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.

64Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 67 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.957
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
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 — 30 of the last 100 commits are automated dependency updates
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.3
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/15 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes5,360
source_files_sampled15
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

211GitHub stars
10contributors
9commits, last 12 months
42days since last push
8releases
1bus factor
11open 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 ★ / 43 ⇿
0Stars
43Forks
6Releases

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.

010203040504322023-082025-022026-09
Major 0Minor 0Patch 6

Each point covers 3 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 12:45 UTC

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

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

RegistryPackageVersionRelation
npmreadline-sync1.4.10direct
npmshelljs0.10.0direct
npm@cspotcode/source-map-support0.8.1indirect
npm@isaacs/balanced-match4.0.1indirect
npm@isaacs/brace-expansion5.0.0indirect
npm@isaacs/cliui8.0.2indirect
npm@jridgewell/resolve-uri3.1.0indirect
npm@jridgewell/sourcemap-codec1.4.14indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@tsconfig/node101.0.9indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.3indirect
npm@types/node24.0.13indirect
npm@types/readline-sync1.4.8indirect
npm@types/shelljs0.8.17indirect
npmacorn8.8.0indirect
npmacorn-walk8.2.0indirect
npmansi-regex5.0.1indirect
npmansi-regex6.1.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmanymatch3.1.3indirect
npmarg4.1.3indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.3.0indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.3indirect
npmchokidar3.6.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcreate-require1.1.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.3.7indirect
npmdiff4.0.2indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmexeca5.1.1indirect
npmfast-glob3.3.3indirect
npmfastq1.19.1indirect
npmfill-range7.1.1indirect
npmforeground-child3.3.1indirect
npmfsevents2.3.3indirect
npmget-stream6.0.1indirect
npmglob11.0.3indirect
npmglob-parent5.1.2indirect
npmhas-flag3.0.0indirect
npmhuman-signals2.1.0indirect
npmignore-by-default1.0.1indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-stream2.0.1indirect
npmisexe2.0.0indirect
npmjackspeak4.1.1indirect
npmlru-cache11.1.0indirect
npmmake-error1.3.6indirect
npmmerge-stream2.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmmimic-fn2.1.0indirect
npmminimatch10.0.3indirect
npmminimatch3.1.2indirect
npmminipass7.1.2indirect
npmms2.1.3indirect
npmnodemon3.1.10indirect
npmnormalize-path3.0.0indirect
npmnpm-run-path4.0.1indirect
npmonetime5.1.2indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-key3.1.1indirect
npmpath-scurry2.0.0indirect
npmpicomatch2.3.1indirect
npmprettier3.6.2indirect
npmpstree.remy1.1.8indirect
npmqueue-microtask1.2.3indirect
npmreaddirp3.6.0indirect
npmreusify1.1.0indirect
npmrun-parallel1.2.0indirect
npmsemver7.6.3indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit3.0.7indirect
npmsignal-exit4.1.0indirect
npmsimple-update-notifier2.0.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmstrip-final-newline2.0.0indirect
npmsupports-color5.5.0indirect
npmto-regex-range5.0.1indirect
npmtouch3.1.1indirect
npmts-node10.9.2indirect
npmtypescript5.8.3indirect
npmundefsafe2.0.5indirect
npmundici-types7.8.0indirect
npmv8-compile-cache-lib3.0.1indirect
npmwhich2.0.2indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmyn3.1.1indirect
Dependency advisories 0

Installing npm:nodejs-whisper@0.3.1 pulls in 36 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.