Public recordGood
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 09:02 UTC
nk2028 / opencc-js
The JavaScript version of Open Chinese Convert (OpenCC)
nk2028/opencc-js holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on Security (45/100). It was last updated 6 days ago. 2 contributors account for most of its recent work.
78
overall / 100Software 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.
78
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)
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).
Ownership
nk2028Organization
201 followers65 public repossince Apr 2020
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | opencc-js | 1.4.1 | 440,383 | 30 | 6 days ago | openccchineseunicodechinese-languagesimplified-chinesetraditional-chinesechinese-characters |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
73
Development activity
65Good
How it's scored
| 36/36 | Push recency — last push 6 days ago |
| 4.8/36 | Commit cadence — 7/52 weeks with commits |
| 14.1/18 | Commit volume — 36 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 36 |
| human_commit_share | — |
| days_since_last_push | 6 |
| active_weeks_last_year | 7 |
Release discipline
84Excellent
How it's scored
| 27/27 | Ships releases — 22 releases published |
| 36/36 | Release recency — latest release 6 days ago |
| 12.6/27 | Release cadence — a release every ~216.2 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 22 |
| latest_release_tag | v1.4.1 |
| releases_from_tags | no |
| days_since_latest_release | 6 |
| mean_days_between_releases | 216.2 |
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?
65
Popularity & adoption
59Moderate
How it's scored
| 41.2/60 | Stars — 346 stars |
| 13/25 | Forks — 37 forks |
| 5/15 | Watchers — 9 watchers |
Inputs used
| forks | 37 |
| stars | 346 |
| watchers | 9 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
50Moderate
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
94Exceptional
How it's scored
| 75.3/80 | Monthly downloads — 440,383 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | opencc-js |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 440,383 |
| 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?
79
Maintainer resilience (bus factor)
61Moderate
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 13.9/22.5 | Commit distribution — top contributor authored 38% of commits |
| 12.2/13.5 | Contributor breadth — 9 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 9 |
| top_contributor_share | 0.382 |
How it's scored
| 38/42 | Issue resolution — 90% of issues closed |
| 26.5/30 | PR acceptance — 23/26 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 1/27 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 23 |
| open_issues | 2 |
| closed_issues | 19 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.905 |
| closed_unmerged_prs | 3 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
89Excellent
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 16.6/25 | Owner reach — 201 followers of nk2028 |
| 25/25 | Track record — 65 public repos, account ~6 yr old |
Inputs used
| followers | 201 |
| owner_type | Organization |
| is_verified | — |
| owner_login | nk2028 |
| public_repos | 65 |
| account_age_days | 2,290 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on npm |
| 35/35 | Publish recency — latest publish 6 days ago |
| 20/20 | Version history — 30 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | opencc-js |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 6 |
Engineering Quality
Are baseline engineering and documentation practices in place?
67
Engineering practices
68Good
How it's scored
| 24/24 | CI workflows — 3 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
65Good
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://www.npmjs.com/package/opencc-js |
| 10/10 | Repository description |
| 10/10 | Topics — 3 topics |
| 0/10 | Wiki |
Inputs used
| topics | chinese-characters, traditional-chinese, simplified-chinese |
| has_wiki | no |
| homepage | https://www.npmjs.com/package/opencc-js |
| docs_site | https://www.npmjs.com/package/opencc-js |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
45
Security posture
45Weak
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 2.5/2.5 | CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 1/27 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 6 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 1.5/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 4.5 |
Excluded from scoring (no data or not applicable): Packaging, 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.
56
Agent context & guidance
75Good
How it's scored
| 45/45 | Agent instructions — AGENTS.md, CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | AGENTS.md, CLAUDE.md |
| agent_instruction_max_bytes | 2,322 |
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — lockfile |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 3/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | package-lock.json |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | — |
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
Code legibility for models
55Moderate
How it's scored
| 0/45 | Type-checkable code — JavaScript without a type-check config |
| 55/55 | Manageable file sizes — 0/16 source files over 60KB |
Inputs used
| primary_language | JavaScript |
| largest_source_bytes | 15,380 |
| source_files_sampled | 16 |
| oversized_source_files | 0 |
Key facts
346GitHub stars
9contributors
36commits, last 12 months
6days since last push
22releases
2bus factor
2open issues
npmpackage ecosystems
More detail
OpenSSF Scorecard 4.5 / 10
4.5aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| 10 | CI-Tests | 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 1/27 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 6 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 3 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 3 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
All dependencies 98
Full resolved dependency set from the GitHub dependency graph: 0 direct and 98 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | @babel/code-frame | 7.18.6 | indirect |
| npm | @babel/helper-validator-identifier | 7.19.1 | indirect |
| npm | @babel/highlight | 7.18.6 | indirect |
| npm | @jridgewell/gen-mapping | 0.3.13 | indirect |
| npm | @jridgewell/resolve-uri | 3.1.2 | indirect |
| npm | @jridgewell/source-map | 0.3.11 | indirect |
| npm | @jridgewell/sourcemap-codec | 1.5.5 | indirect |
| npm | @jridgewell/trace-mapping | 0.3.31 | indirect |
| npm | @rollup/plugin-terser | 1.0.0 | indirect |
| npm | @rollup/rollup-android-arm-eabi | 4.60.2 | indirect |
| npm | @rollup/rollup-android-arm64 | 4.60.2 | indirect |
| npm | @rollup/rollup-darwin-arm64 | 4.60.2 | indirect |
| npm | @rollup/rollup-darwin-x64 | 4.60.2 | indirect |
| npm | @rollup/rollup-freebsd-arm64 | 4.60.2 | indirect |
| npm | @rollup/rollup-freebsd-x64 | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-arm-gnueabihf | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-arm-musleabihf | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-arm64-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-arm64-musl | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-loong64-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-loong64-musl | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-ppc64-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-ppc64-musl | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-riscv64-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-riscv64-musl | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-s390x-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-x64-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-linux-x64-musl | 4.60.2 | indirect |
| npm | @rollup/rollup-openbsd-x64 | 4.60.2 | indirect |
| npm | @rollup/rollup-openharmony-arm64 | 4.60.2 | indirect |
| npm | @rollup/rollup-win32-arm64-msvc | 4.60.2 | indirect |
| npm | @rollup/rollup-win32-ia32-msvc | 4.60.2 | indirect |
| npm | @rollup/rollup-win32-x64-gnu | 4.60.2 | indirect |
| npm | @rollup/rollup-win32-x64-msvc | 4.60.2 | indirect |
| npm | @types/estree | 1.0.8 | indirect |
| npm | @types/normalize-package-data | 2.4.1 | indirect |
| npm | acorn | 8.16.0 | indirect |
| npm | ansi-styles | 3.2.1 | indirect |
| npm | assertion-error | 1.1.0 | indirect |
| npm | buffer-from | 1.1.2 | indirect |
| npm | chai | 4.3.7 | indirect |
| npm | chalk | 2.4.2 | indirect |
| npm | check-error | 1.0.2 | indirect |
| npm | color-convert | 1.9.3 | indirect |
| npm | color-name | 1.1.3 | indirect |
| npm | commander | 2.20.3 | indirect |
| npm | deep-eql | 4.1.2 | indirect |
| npm | detect-indent | 5.0.0 | indirect |
| npm | error-ex | 1.3.2 | indirect |
| npm | escape-string-regexp | 1.0.5 | indirect |
| npm | fsevents | 2.3.3 | indirect |
| npm | function-bind | 1.1.1 | indirect |
| npm | get-func-name | 2.0.2 | indirect |
| npm | graceful-fs | 4.2.10 | indirect |
| npm | has | 1.0.3 | indirect |
| npm | has-flag | 3.0.0 | indirect |
| npm | hosted-git-info | 2.8.9 | indirect |
| npm | imurmurhash | 0.1.4 | indirect |
| npm | is-arrayish | 0.2.1 | indirect |
| npm | is-core-module | 2.11.0 | indirect |
| npm | is-plain-obj | 1.1.0 | indirect |
| npm | js-tokens | 4.0.0 | indirect |
| npm | json-parse-even-better-errors | 2.3.1 | indirect |
| npm | jsonc-parser | 3.3.1 | indirect |
| npm | lines-and-columns | 1.2.4 | indirect |
| npm | loupe | 2.3.6 | indirect |
| npm | make-dir | 2.1.0 | indirect |
| npm | normalize-package-data | 2.5.0 | indirect |
| npm | opencc-data | 1.4.1 | indirect |
| npm | parse-json | 5.2.0 | indirect |
| npm | path-parse | 1.0.7 | indirect |
| npm | pathval | 1.1.1 | indirect |
| npm | pify | 4.0.1 | indirect |
| npm | read-pkg | 5.2.0 | indirect |
| npm | resolve | 1.22.1 | indirect |
| npm | rollup | 4.60.2 | indirect |
| npm | rollup-plugin-generate-package-json | 3.2.0 | indirect |
| npm | semver | 5.7.2 | indirect |
| npm | serialize-javascript | 7.0.5 | indirect |
| npm | signal-exit | 3.0.7 | indirect |
| npm | smob | 1.6.1 | indirect |
| npm | sort-keys | 2.0.0 | indirect |
| npm | source-map | 0.6.1 | indirect |
| npm | source-map-support | 0.5.21 | indirect |
| npm | spdx-correct | 3.1.1 | indirect |
| npm | spdx-exceptions | 2.3.0 | indirect |
| npm | spdx-expression-parse | 3.0.1 | indirect |
| npm | spdx-license-ids | 3.0.12 | indirect |
| npm | supports-color | 5.5.0 | indirect |
| npm | supports-preserve-symlinks-flag | 1.0.0 | indirect |
| npm | terser | 5.46.2 | indirect |
| npm | type-detect | 4.0.8 | indirect |
| npm | type-fest | 0.4.1 | indirect |
| npm | type-fest | 0.6.0 | indirect |
| npm | validate-npm-package-license | 3.0.4 | indirect |
| npm | write-file-atomic | 2.4.3 | indirect |
| npm | write-json-file | 3.2.0 | indirect |
| npm | write-pkg | 4.0.0 | indirect |
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.
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.14.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — npm.