Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 07:34 UTC

phensley / cldr-engine

Internationalization and localization in Typescript with Unicode CLDR, batteries included

TypeScriptApache-2.0★ 60 stars⑂ 3 forkssince Jan 2018archivedView on GitHub ↗
KindCommand-line toolLibraryhow this is determined

phensley/cldr-engine holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (62/100) and lowest on AI Readiness (36/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

19
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

Patrick HensleyPersonal account
64 followers36 public repossince Feb 2009Independent researcher

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@phensley/cldr1.16.018,99525139 days agocldrunicodei18nintlinternationalizationlocalematharbitrary-precisionpluralizationdecimalglobalize
npm@phensley/locale1.16.0104,1419439 days ago—
npm@phensley/decimal1.16.016,48720939 days ago—
npm@phensley/plurals1.16.015,99310839 days ago—
npm@phensley/timezone1.16.022,75916439 days ago—
npm@phensley/cldr-core1.16.016,90825139 days ago—
npm@phensley/cldr-types1.16.015,84410339 days ago—
npm@phensley/cldr-utils1.16.023,00918739 days ago—

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
18/36Push recency — last push 39 days ago
11.8/36Commit cadence — 17/52 weeks with commits
16.2/18Commit volume — 63 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year63
human_commit_share1
days_since_last_push39
active_weeks_last_year17
How it's scored
27/27Ships releases — 100 releases published
16.2/36Release recency — latest release 345 days ago
27/27Release cadence — a release every ~42.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv1.14.0
releases_from_tagsno
days_since_latest_release345
mean_days_between_releases42.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?

53Moderate · 17% of overall
How it's scored
28.7/60Stars — 60 stars
2.5/25Forks — 3 forks
2.7/15Watchers — 4 watchers
Inputs used
forks3
stars60
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges11
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, badgen.net, github.com
has_pull_request_templateno
How it's scored
71.6/80Monthly downloads — 234,136 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@phensley/cldr, @phensley/locale, @phensley/decimal, @phensley/plurals, @phensley/timezone, @phensley/cldr-core, @phensley/cldr-types, @phensley/cldr-utils
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads234,136
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.998
How it's scored
36/42Issue resolution — 86% of issues closed
30/30PR acceptance — 4/4 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs4
open_issues1
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.857
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
13/25Owner reach — 64 followers of phensley
23.4/25Track record — 36 public repos, account ~17 yr old
Inputs used
followers64
owner_typeUser
is_verified—
owner_loginphensley
public_repos36
account_age_days6,457
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 39 days ago
20/20Version history — 251 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@phensley/cldr, @phensley/locale, @phensley/decimal, @phensley/plurals, @phensley/timezone, @phensley/cldr-core, @phensley/cldr-types, @phensley/cldr-utils
ecosystemsnpm
any_deprecatedno
min_days_since_publish39

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 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
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://phensley.github.io/cldr-engine/
10/10Repository description
10/10Topics — 15 topics
0/10Wiki
Inputs used
topicsinternationalization, typescript, unicode, cldr, arbitrary-precision, i18n, math, language, locale, decimal, pluralization, timezone, localization, globalize, messageformat
has_wikino
homepagehttps://phensley.github.io/cldr-engine/
docs_sitehttps://phensley.github.io/cldr-engine/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project is archived
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages11
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@phensley/cldr@1.16.0 runtime dependency closure — what installing the published package pulls in — 11 packages. Reachability is not analyzed.

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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.9/40Legible commit history — 13 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.13
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/cldr-compiler/tsconfig.json, packages/cldr-core/tsconfig.json, packages/cldr-ext-rbnf/tsconfig.json, packages/cldr-types/tsconfig.json, packages/cldr-utils/tsconfig.json, packages/cldr/tsconfig.json, packages/decimal/tsconfig.json, packages/language-tag/tsconfig.json, packages/locale-matcher/tsconfig.json, packages/locale/tsconfig.json, packages/messageformat/tsconfig.json, packages/plurals/tsconfig.json, packages/timezone/tsconfig.json, packages/unit-converter/tsconfig.json, tsconfig.json
0/10Reproducible environment
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/cldr-compiler/tsconfig.json, packages/cldr-core/tsconfig.json, packages/cldr-ext-rbnf/tsconfig.json, packages/cldr-types/tsconfig.json, packages/cldr-utils/tsconfig.json, packages/cldr/tsconfig.json, packages/decimal/tsconfig.json, packages/language-tag/tsconfig.json, packages/locale-matcher/tsconfig.json, packages/locale/tsconfig.json, packages/messageformat/tsconfig.json, packages/plurals/tsconfig.json, packages/timezone/tsconfig.json, packages/unit-converter/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.9/55Manageable file sizes — 1/515 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes129,846
source_files_sampled515
oversized_source_files1

Key facts

60GitHub stars
3contributors
63commits, last 12 months
39days since last push
100releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
36Releases

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.

12233312020-072022-122025-06
Major 0Minor 9Patch 27

Each point covers 5 days.

OpenSSF Scorecard 3.1 / 10
3.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-10-18 07:34 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 58
RegistryPackageVersion constraintManifest
npm@phensley/cldr-coreworkspace:~1.16.0packages/cldr-compiler/package.json
npm@phensley/cldr-ext-rbnfworkspace:~1.16.0packages/cldr-compiler/package.json
npm@phensley/cldr-typesworkspace:~1.16.0packages/cldr-compiler/package.json
npm@phensley/cldr-utilsworkspace:~1.16.0packages/cldr-compiler/package.json
npm@phensley/decimalworkspace:~1.16.0packages/cldr-compiler/package.json
npm@phensley/timezoneworkspace:~1.16.0packages/cldr-compiler/package.json
npm@prettier/sync^0.6.1packages/cldr-compiler/package.json
npm@types/node-fetch^2.6.2packages/cldr-compiler/package.json
npm@types/yargs^17.0.35packages/cldr-compiler/package.json
npmchalk^4.1.2packages/cldr-compiler/package.json
npmfast-json-patch^3.1.1packages/cldr-compiler/package.json
npmminimatch^7.4.6packages/cldr-compiler/package.json
npmnode-fetch^2.6.7packages/cldr-compiler/package.json
npmpartial.lenses^14.17.0packages/cldr-compiler/package.json
npmprettier^3.8.3packages/cldr-compiler/package.json
npmtar^7.5.13packages/cldr-compiler/package.json
npmtslib^2.8.1packages/cldr-compiler/package.json
npmyaml^2.8.3packages/cldr-compiler/package.json
npmyargs^17.7.2packages/cldr-compiler/package.json
npm@phensley/cldr-typesworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/cldr-utilsworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/decimalworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/language-tagworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/localeworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/locale-matcherworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/messageformatworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/pluralsworkspace:~1.16.0packages/cldr-core/package.json
npm@phensley/timezoneworkspace:~1.16.0packages/cldr-core/package.json
npmtslib^2.8.1packages/cldr-core/package.json
npm@phensley/cldr-typesworkspace:~1.16.0packages/cldr-ext-rbnf/package.json
npm@phensley/decimalworkspace:~1.16.0packages/cldr-ext-rbnf/package.json
npm@phensley/pluralsworkspace:~1.16.0packages/cldr-ext-rbnf/package.json
npmtslib^2.8.1packages/cldr-ext-rbnf/package.json
npmtslib^2.8.1packages/cldr-types/package.json
npmtslib^2.8.1packages/cldr-utils/package.json
npm@phensley/cldr-coreworkspace:~1.16.0packages/cldr/package.json
npm@phensley/cldr-utilsworkspace:~1.16.0packages/cldr/package.json
npm@phensley/messageformatworkspace:~1.16.0packages/cldr/package.json
npmtslib^2.8.1packages/cldr/package.json
npmtslib^2.8.1packages/decimal/package.json
npmtslib^2.8.1packages/language-tag/package.json
npm@phensley/language-tagworkspace:~1.16.0packages/locale-matcher/package.json
npm@phensley/localeworkspace:~1.16.0packages/locale-matcher/package.json
npmtslib^2.8.1packages/locale-matcher/package.json
npm@phensley/language-tagworkspace:~1.16.0packages/locale/package.json
npmtslib^2.8.1packages/locale/package.json
npm@phensley/cldr-utilsworkspace:~1.16.0packages/messageformat/package.json
npm@phensley/decimalworkspace:~1.16.0packages/messageformat/package.json
npm@phensley/pluralsworkspace:~1.16.0packages/messageformat/package.json
npmtslib^2.8.1packages/messageformat/package.json
npm@phensley/decimalworkspace:~1.16.0packages/plurals/package.json
npmtslib^2.8.1packages/plurals/package.json
npm@phensley/cldr-utilsworkspace:~1.16.0packages/timezone/package.json
npmtslib^2.8.1packages/timezone/package.json
npm@phensley/cldr-typesworkspace:~1.16.0packages/unit-converter/package.json
npm@phensley/cldr-utilsworkspace:~1.16.0packages/unit-converter/package.json
npm@phensley/decimalworkspace:~1.16.0packages/unit-converter/package.json
npmtslib^2.8.1packages/unit-converter/package.json
All dependencies 50

Full resolved dependency set from the GitHub dependency graph: 13 direct and 37 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@prettier/sync^0.6.1direct
npm@types/node-fetch^2.6.2direct
npm@types/yargs^17.0.35direct
npmchalk^4.1.2direct
npmfast-json-patch^3.1.1direct
npmminimatch^7.4.6direct
npmnode-fetch^2.6.7direct
npmpartial.lenses^14.17.0direct
npmprettier^3.8.3direct
npmtar^7.5.13direct
npmtslib^2.8.1direct
npmyaml^2.8.3direct
npmyargs^17.7.2direct
npm@eslint/compat^2.0.5indirect
npm@js-temporal/polyfill0.5.1indirect
npm@microsoft/api-documenter^7.30.5indirect
npm@microsoft/api-extractor~7.58.7indirect
npm@rollup/plugin-commonjs^29.0.2indirect
npm@rollup/plugin-json^6.1.0indirect
npm@rollup/plugin-node-resolve^16.0.3indirect
npm@rollup/plugin-terser^1.0.0indirect
npm@types/node^24.10.1indirect
npm@types/node^24.12.0indirect
npm@typescript-eslint/eslint-plugin^8.59.1indirect
npm@typescript-eslint/parser^8.59.1indirect
npm@vitest/coverage-istanbul^4.1.5indirect
npmbeautify-benchmark^0.2.4indirect
npmbenchmark^2.1.4indirect
npmdependency-cruiser^17.3.10indirect
npmdts-bundle-generator^9.5.1indirect
npmeslint^10.2.1indirect
npmeslint-config-prettier^10.1.8indirect
npmeslint-plugin-prettier^5.5.5indirect
npmjiti^2.6.1indirect
npmjsdom^29.1.1indirect
npmnpm-check-updates^22.0.1indirect
npmrimraf^6.1.3indirect
npmrollup^4.60.2indirect
npmrollup-plugin-dts^6.4.1indirect
npmrollup-plugin-filesize^10.0.0indirect
npmrollup-plugin-sourcemaps^0.6.3indirect
npmrollup-plugin-typescript2^0.37.0indirect
npmsource-map-explorer^2.5.3indirect
npmterser^5.46.2indirect
npmts-node^10.9.2indirect
npmtsx^4.21.0indirect
npmtypedoc^0.28.19indirect
npmtypescript~5.9.3indirect
npmtypescript-eslint^8.59.1indirect
npmvitest^4.1.5indirect
Dependency advisories 0

Installing npm:@phensley/cldr@1.16.0 pulls in 11 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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 — npm.