Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 01:08 UTC

locize / locize-cli

locize cli to import / export locales, add / edit / remove, sync segments

JavaScriptMIT★ 71 stars⑂ 23 forkssince Apr 2016View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

locize/locize-cli holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on AI Readiness (29/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

locizeOrganization
22 followers68 public repossince Feb 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmlocize-cli12.5.0199,6582423 days agoclilocize

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
13.2/36Commit cadence19/52 weeks with commits
17/18Commit volume78 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year78
human_commit_share
days_since_last_push3
active_weeks_last_year19
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~15 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv12.5.0
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases15

Community & Adoption

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

61Moderate · 17% of overall
How it's scored
29.9/60Stars71 stars
11.2/25Forks23 forks
0/15Watchers2 watchers
Inputs used
forks23
stars71
watchers2
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
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateyes
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
70.7/80Monthly downloads199,658 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageslocize-cli
dependents
ecosystemsnpm
total_downloads
monthly_downloads199,658
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.5/22.5Commit distributiontop contributor authored 98% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.977
How it's scored
42/42Issue resolution100% of issues closed
18.5/30PR acceptance8/13 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs8
open_issues0
closed_issues102
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs5
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.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
9.8/25Owner reach22 followers of locize
25/25Track record68 public repos, account ~10 yr old
Inputs used
followers22
owner_typeOrganization
is_verified
owner_loginlocize
public_repos68
account_age_days3,805
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 3 days ago
20/20Version history242 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageslocize-cli
ecosystemsnpm
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicslocize, cli, language, translation-files, namespace, android, sync, synchronization
has_wikiyes
homepage
docs_site
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-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Packaging. 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
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.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/79 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes49,075
source_files_sampled79
oversized_source_files0

Key facts

71GitHub stars
7contributors
78commits, last 12 months
3days since last push
100releases
1bus factor
0open 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).Scorecard v5.5.0 · 2026-07-19 01:07 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 24
RegistryPackageVersion constraintManifest
npm@js.properties/properties0.5.4package.json
npmandroid-string-resource2.3.10package.json
npmcacheable-lookup6.1.0package.json
npmcolors1.4.0package.json
npmcommander14.0.3package.json
npmdiff8.0.4package.json
npmdotenv17.4.2package.json
npmfast-csv5.0.7package.json
npmflat5.0.2package.json
npmfluent_conv3.3.0package.json
npmgettext-converter1.3.3package.json
npmhttps-proxy-agent7.0.6package.json
npmini6.0.0package.json
npmlaravelphp2.0.4package.json
npmlocize-xcstrings2.0.0package.json
npmlodash.clonedeep4.5.0package.json
npmmkdirp3.0.1package.json
npmresx2.0.4package.json
npmrimraf6.1.3package.json
npmstrings-file0.0.5package.json
npmtmexchange2.0.6package.json
npmxliff6.4.0package.json
npmxlsxhttps://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgzpackage.json
npmyaml2.9.0package.json
All dependencies 32

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

RegistryPackageVersionRelation
npm@js.properties/properties0.5.4direct
npmandroid-string-resource2.3.10direct
npmcacheable-lookup6.1.0direct
npmcolors1.4.0direct
npmcommander14.0.3direct
npmdiff8.0.4direct
npmdotenv17.4.2direct
npmfast-csv5.0.7direct
npmflat5.0.2direct
npmfluent_conv3.3.0direct
npmgettext-converter1.3.3direct
npmhttps-proxy-agent7.0.6direct
npmini6.0.0direct
npmlaravelphp2.0.4direct
npmlocize-xcstrings2.0.0direct
npmlodash.clonedeep4.5.0direct
npmmkdirp3.0.1direct
npmresx2.0.4direct
npmrimraf6.1.3direct
npmstrings-file0.0.5direct
npmtmexchange2.0.6direct
npmxliff6.4.0direct
npmyaml2.9.0direct
npm@rollup/plugin-replace6.0.3indirect
npm@rollup/plugin-terser1.0.0indirect
npm@yao-pkg/pkg6.21.0indirect
npmeslint9.39.2indirect
npmeslint-plugin-import2.32.0indirect
npmgh-release8.1.0indirect
npmneostandard0.13.0indirect
npmrollup4.62.2indirect
npmvitest4.1.10indirect
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.14.0 — full methodology · metrics wiki.

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