Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 07:22 UTC

zh-lx / pinyin-pro

中文转拼音、拼音音调、拼音声母、拼音韵母、多音字拼音、姓氏拼音、拼音匹配、中文分词

TypeScriptMIT★ 4,690 stars⑂ 393 forkssince Oct 2020View on GitHub ↗

zh-lx/pinyin-pro holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on Security (42/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

zhoulixiangPersonal account
418 followers18 public repossince Oct 2020KuaiShou

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
npm@pinyin-pro/datapoints to another repo — not scored1.3.110,52013184 days ago
npmpinyin-pro3.29.31,279,9931559 days agopinyin

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
6.9/36Commit cadence10/52 weeks with commits
18/18Commit volume114 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year114
human_commit_share1
days_since_last_push4
active_weeks_last_year10
How it's scored
27/27Ships releases72 releases published
36/36Release recencylatest release 9 days ago
19.8/27Release cadencea release every ~82.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count72
latest_release_tag3.29.3
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases82.5
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?

78Good · 17% of overall
How it's scored
59.5/60Stars4,690 stars
21.6/25Forks393 forks
7.9/15Watchers27 watchers
Inputs used
forks393
stars4,690
watchers27
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads1,279,993 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespinyin-pro
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,279,993
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?

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.6/22.5Commit distributiontop contributor authored 88% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.885
How it's scored
41.2/42Issue resolution98% of issues closed
28.1/30PR acceptance177/189 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/17 approved changesets -- score normalized to 1
Inputs used
merged_prs177
open_issues3
closed_issues161
prs_merged_7d2
prs_decided_7d2
prs_merged_30d21
prs_decided_30d25
issue_closed_ratio0.982
closed_unmerged_prs12
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
18.9/25Owner reach418 followers of zh-lx
21/25Track record18 public repos, account ~5 yr old
Inputs used
followers418
owner_typeUser
is_verified
owner_loginzh-lx
public_repos18
account_age_days2,139
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 npm
35/35Publish recencylatest publish 9 days ago
20/20Version history155 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespinyin-pro
ecosystemsnpm
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pinyin-pro.cn
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicspinyin-pro, pinyin, hanzi, hanzi-pinyin, hanzi2pinyin, js-pinyin, pinyin-match
has_wikiyes
homepagehttps://pinyin-pro.cn
docs_sitehttps://pinyin-pro.cn
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 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
2.5/2.5CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/17 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 6 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 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
2.5/5SASTSAST tool is not run on all commits -- score normalized to 5
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities19 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Signed-Releases. 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.

74Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.99
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes355
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc
11/11Static type checkingpackages/data/tsconfig.json, packages/pinyin-pro/scripts/tsconfig.json, packages/pinyin-pro/tsconfig.json
10/10Reproducible environmentlockfile
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-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/data/tsconfig.json, packages/pinyin-pro/scripts/tsconfig.json, packages/pinyin-pro/tsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
52.7/55Manageable file sizes5/121 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,946,528
source_files_sampled121
oversized_source_files5

Key facts

4,690GitHub stars
19contributors
114commits, last 12 months
4days since last push
72releases
1bus factor
3open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package '@pinyin-pro/data' points at a different repository (https://github.com/chinese-data/pinyin-pro-data); 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 ★ / 393 ⇿
0Stars
393Forks
72Releases

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.

0100200300400390252020-102023-092026-08
Major 0Minor 26Patch 46

Each point covers 6 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-28 07:22 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/17 approved changesets -- score normalized to 1
10Contributorsproject has 6 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 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5SASTSAST tool is not run on all commits -- score normalized to 5
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities19 existing vulnerabilities detected
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 statisticsnpm.