Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-15 22:45 UTC

sathiyatskrj / Speechmate

Speechmate – A bilingual classroom assistant prototype for English ↔ Nicobarese and other tribal language communication. Includes Child Mode with picture-based learning and Teacher Mode with phrase translation. Created by T Sathiya Moorthy.

C++ · C · DartApache-2.0★ 2 stars⑂ 2 forkssince Dec 2025View on GitHub ↗
KindMobile applicationhow this is determined

sathiyatskrj/Speechmate holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (69/100) and lowest on Community & Adoption (43/100). It was last updated 165 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

sathiyatskrjPersonal account
0 followers6 public repossince Dec 2020

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

Metrics by category

Vitality

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

61Moderate · 21% of overall
How it's scored
9.9/36Push recency — last push 165 days ago
9.7/36Commit cadence — 14/52 weeks with commits
18/18Commit volume — 803 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year803
human_commit_share1
days_since_last_push165
active_weeks_last_year14
How it's scored
27/27Ships releases — 23 releases published
27/36Release recency — latest release 171 days ago
27/27Release cadence — a release every ~16.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv1.5.0
releases_from_tagsno
days_since_latest_release171
mean_days_between_releases16.6

Community & Adoption

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

43Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
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?

46Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.9/22.5Commit distribution — top contributor authored 60% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.604
How it's scored
0/42Issue resolution — no issues or no data
24.6/30PR acceptance — 64/78 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs64
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs14
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
0/25Owner reach — 0 followers of sathiyatskrj
17.9/25Track record — 6 public repos, account ~5 yr old
Inputs used
followers0
owner_typeUser
is_verified—
owner_loginsathiyatskrj
public_repos6
account_age_days2,145
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
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?

55Moderate · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfiles — go.sum
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesgo.sum
manifestsandroid/build.gradle
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno

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.

69Good · 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 — 93 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.93
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — android/app/src/main/cpp/whisper/Makefile, android/app/src/main/cpp/whisper/bindings/go/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesandroid/app/src/main/cpp/whisper/Makefile, android/app/src/main/cpp/whisper/bindings/go/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsandroid/app/build.gradle, android/app/src/main/cpp/whisper/bindings/go/go.mod, android/app/src/main/cpp/whisper/bindings/java/build.gradle, android/app/src/main/cpp/whisper/examples/whisper.android.java/app/build.gradle, android/app/src/main/cpp/whisper/examples/whisper.android.java/build.gradle, android/app/src/main/cpp/whisper/examples/whisper.android/app/build.gradle, android/app/src/main/cpp/whisper/examples/whisper.android/build.gradle, android/app/src/main/cpp/whisper/examples/whisper.android/lib/build.gradle, android/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C++ (statically typed)
52.4/55Manageable file sizes — 16/336 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes960,825
source_files_sampled336
oversized_source_files16
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 — examples, samples
Inputs used
example_dirsexamples, samples
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

2GitHub stars
3contributors
803commits, last 12 months
165days since last push
23releases
1bus factor
0open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/11/15 22:44:29 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
1Releases

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.

111222212025-122025-122025-12
Major 1Minor 0Patch 0
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.34.0 — full methodology · metrics wiki.

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