Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-05 02:40 UTC

cjpais / Handy

A free, open source, and extensible speech-to-text application that works completely offline.

Rust · TypeScriptMIT★ 28,707 stars⑂ 2,514 forkssince Feb 2025View on GitHub ↗
KindDesktop applicationWeb interfaceCommand-line toolLibraryhow this is determined

cjpais/Handy holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Security (41/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

87
overall / 100
Excellent

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.

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

Ownership

CJ PaisPersonal account
788 followers110 public repossince Mar 2012

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
crates.iohandypoints to another repo — not scored0.1.41,95452239 days agogenerationalhandlestableindexdata-structuresmemory-managementno-std

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
33.9/36Commit cadence49/52 weeks with commits
18/18Commit volume531 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year531
human_commit_share1
days_since_last_push1
active_weeks_last_year49

Release discipline

98Exceptional
How it's scored
27/27Ships releases62 releases published
36/36Release recencylatest release 14 days ago
27/27Release cadencea release every ~13.8 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count62
latest_release_tagv0.9.4
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases13.8

Community & Adoption

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

87Excellent · 17% of overall
How it's scored
60/60Stars28,707 stars
25/25Forks2,514 forks
10.6/15Watchers83 watchers
Inputs used
forks2,514
stars28,707
watchers83
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.6/22.5Commit distributiontop contributor authored 71% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.708
How it's scored
36.7/42Issue resolution87% of issues closed
17.3/30PR acceptance369/640 decided PRs merged
4.9/13Newcomer PR acceptance6/16 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 14/30 approved changesets -- score normalized to 4
Inputs used
merged_prs369
open_issues83
closed_issues570
prs_merged_7d14
prs_decided_7d32
prs_merged_30d27
prs_decided_30d58
issue_closed_ratio0.873
closed_unmerged_prs271
first_time_authors_30d11
first_time_prs_merged_30d6
first_time_prs_decided_30d16
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20.8/25Owner reach788 followers of cjpais
25/25Track record110 public repos, account ~14 yr old
Inputs used
followers788
owner_typeUser
is_verified
owner_logincjpais
public_repos110
account_age_days5,249
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows9 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests18 out of 24 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://handy.computer
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsspeech-to-text, tauri-v2, accessibility, cross-platform
has_wikiyes
homepagehttps://handy.computer
docs_sitehttps://handy.computer
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.8/2.5CI-Tests18 out of 24 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 14/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 4 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.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
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
0/5Security-Policysecurity policy file not 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
0/7.5Vulnerabilities72 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Packaging. 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history77 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.77
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes9,330
How it's scored
12.6/18One-command bootstrapsrc-tauri/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingtsconfig.json
10/10Reproducible environmentNix, lockfile
10/10Demonstrated agent practice8 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixyes
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.08
toolchain_manifestssrc-tauri/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
54.5/55Manageable file sizes2/210 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes123,111
source_files_sampled210
oversized_source_files2

Key facts

28,707GitHub stars
100contributors
531commits, last 12 months
1days since last push
62releases
1bus factor
83open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 34 authors (cap 12)
  • crates package 'handy' points at a different repository (https://github.com/thomcc/handy); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 2,514 ⇿
0Stars
2,514Forks
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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

1,4001,6001,8002,0002,2002,4002,6002,514262026-042026-062026-08
Major 0Minor 1Patch 5
OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-08-05 02:40 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
7CI-Tests18 out of 24 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 14/30 approved changesets -- score normalized to 4
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities72 existing vulnerabilities detected
Direct dependencies 72
RegistryPackageVersion constraintManifest
npm@tailwindcss/vite^4.1.16package.json
npm@tauri-apps/api^2.11.0package.json
npm@tauri-apps/plugin-autostart~2.5.1package.json
npm@tauri-apps/plugin-clipboard-manager~2.3.2package.json
npm@tauri-apps/plugin-dialog~2.6package.json
npm@tauri-apps/plugin-fs~2.4.4package.json
npm@tauri-apps/plugin-global-shortcut~2.3.2package.json
npm@tauri-apps/plugin-opener^2.5.2package.json
npm@tauri-apps/plugin-os~2.3.2package.json
npm@tauri-apps/plugin-process~2.3.1package.json
npm@tauri-apps/plugin-sql~2.3.1package.json
npm@tauri-apps/plugin-store~2.4.1package.json
npm@tauri-apps/plugin-updater~2.10.0package.json
npmi18next^25.7.2package.json
npmimmer^11.1.3package.json
npmlucide-react^0.542.0package.json
npmreact^18.3.1package.json
npmreact-dom^18.3.1package.json
npmreact-i18next^16.4.1package.json
npmreact-markdown^10.1.0package.json
npmreact-select^5.8.0package.json
npmremark-gfm^4.0.1package.json
npmsonner^2.0.7package.json
npmtailwindcss^4.1.16package.json
npmtauri-plugin-macos-permissions-api2.3.0package.json
npmzod^3.25.76package.json
npmzustand^5.0.8package.json
crates.ioonce_cell1src-tauri/Cargo.toml
crates.iotauri2.11.5src-tauri/Cargo.toml
crates.iotauri-plugin-log2.7.1src-tauri/Cargo.toml
crates.iotauri-plugin-opener2.5.2src-tauri/Cargo.toml
crates.iotauri-plugin-store2.4.1src-tauri/Cargo.toml
crates.iotauri-plugin-os2.3.2src-tauri/Cargo.toml
crates.iotauri-plugin-clipboard-manager2.3.2src-tauri/Cargo.toml
crates.iotauri-plugin-macos-permissions2.3.0src-tauri/Cargo.toml
crates.iotauri-plugin-process2.3.1src-tauri/Cargo.toml
crates.iorusqlite_migration2.3src-tauri/Cargo.toml
crates.iotauri-plugin-fs2.4.4src-tauri/Cargo.toml
crates.ioserde1src-tauri/Cargo.toml
crates.ioserde_json1src-tauri/Cargo.toml
crates.iordevsrc-tauri/Cargo.toml
crates.iocpal0.16.0src-tauri/Cargo.toml
crates.ioanyhow1.0.95src-tauri/Cargo.toml
crates.iorubato0.16.2src-tauri/Cargo.toml
crates.iohound3.5.1src-tauri/Cargo.toml
crates.iolog0.4.25src-tauri/Cargo.toml
crates.ioenv_filter0.1.0src-tauri/Cargo.toml
crates.iotokio1.43.0src-tauri/Cargo.toml
crates.iovad-rssrc-tauri/Cargo.toml
crates.ioenigo0.6.1src-tauri/Cargo.toml
crates.iorodiosrc-tauri/Cargo.toml
crates.ioreqwest0.12src-tauri/Cargo.toml
crates.iofutures-util0.3src-tauri/Cargo.toml
crates.iorustfft6.4.0src-tauri/Cargo.toml
crates.iostrsim0.11.0src-tauri/Cargo.toml
crates.ionatural0.5.0src-tauri/Cargo.toml
crates.ioregex1src-tauri/Cargo.toml
crates.iochrono0.4src-tauri/Cargo.toml
crates.iorusqlite0.37src-tauri/Cargo.toml
crates.iotar0.4.44src-tauri/Cargo.toml
crates.ioflate21.0src-tauri/Cargo.toml
crates.iosha20.10src-tauri/Cargo.toml
crates.iotranscribe-rs0.3.8src-tauri/Cargo.toml
crates.iotranscribe-cpp0.1.3src-tauri/Cargo.toml
crates.iohandy-keys0.3.3src-tauri/Cargo.toml
crates.ioferrous-opencc0.2.3src-tauri/Cargo.toml
crates.ioclap4src-tauri/Cargo.toml
crates.iospecta=2.0.0-rc.22src-tauri/Cargo.toml
crates.iospecta-typescript0.0.9src-tauri/Cargo.toml
crates.iotauri-specta=2.0.0-rc.21src-tauri/Cargo.toml
crates.iotauri-plugin-dialog2.6src-tauri/Cargo.toml
crates.iohf-hubsrc-tauri/Cargo.toml
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

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.