Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-18 15:14 UTC

buchwandler / kokorog2p

A unified multi-language G2P (Grapheme-to-Phoneme) library for Kokoro TTS.

PythonApache-2.0★ 4 stars⑂ 3 forkssince Dec 2025View on GitHub ↗

buchwandler/kokorog2p holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (91/100) and lowest on Security (1/100). It was last updated today. 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

buchwandlerOrganization
0 followers18 public repossince Jun 2026

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIkokorog2p0.8.110,083310 days agog2pgrapheme-to-phonemettstext-to-speechkokorophonemizerespeak

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
8.3/36Commit cadence12/52 weeks with commits
18/18Commit volume192 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year192
human_commit_share1
days_since_last_push0
active_weeks_last_year12

Release discipline

100Exceptional
How it's scored
27/27Ships releases34 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~22.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count34
latest_release_tagv0.8.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases22.4

Community & Adoption

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

45Weak · 17% of overall
How it's scored
7.7/60Stars4 stars
2.5/25Forks3 forks
0/15Watchers0 watchers
Inputs used
forks3
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno
How it's scored
53.4/80Monthly downloads10,083 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageskokorog2p
dependents
ecosystemspypi
total_downloads
monthly_downloads10,083
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 factor1 contributor(s) cover half of all commits
0.2/22.5Commit distributiontop contributor authored 99% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.99
How it's scored
21/42Issue resolution50% of issues closed
30/30PR acceptance2/2 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs2
open_issues1
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.5
closed_unmerged_prs0
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of buchwandler
9.6/25Track record18 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginbuchwandler
public_repos18
account_age_days53
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history31 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskokorog2p
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.ruff.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://kokorog2p.readthedocs.io/en/latest/
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsg2p, kokoro, phoneme, text-to-speech, tts
has_wikino
homepagehttps://kokorog2p.readthedocs.io/en/latest/
docs_sitehttps://kokorog2p.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestsdocs/requirements.txt, pyproject.toml, requirements-test.txt, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history93 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
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.ruff.toml
11/11Static type checkingkokorog2p/py.typed
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configskokorog2p/py.typed
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (kokorog2p/py.typed)
55/55Manageable file sizes0/213 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes51,305
source_files_sampled213
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
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

4GitHub stars
3contributors
192commits, last 12 months
0days since last push
34releases
1bus factor
1open issues
PyPIpackage 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
  • deps.dev does not index pypi:kokorog2p@0.8.1; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

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

12233312026-032026-052026-07
Major 0Minor 1Patch 0
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIabbr2words>=0.2.9,<0.3.0pyproject.toml
PyPIspokenform>=0.2.8,<0.3.0pyproject.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 statisticsPyPI.