Public record
Software health reportschema 0.13.0 · metrics 2.10.0 · 2026-07-18 16:15 UTC

tolgee / tolgee-js

Tolgee JavaScript libraries monorepo

TypeScriptMIT★ 259 stars⑂ 37 forkssince Oct 2020View on GitHub ↗

tolgee/tolgee-js holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (82/100) and lowest on Security (50/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

TolgeeOrganization
237 followers47 public repossince Feb 2021

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

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 3 days ago
7.6/36Commit cadence11/52 weeks with commits
13.3/18Commit volume29 commits in the last year
8/10OpenSSF Scorecard: Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year29
human_commit_share
days_since_last_push3
active_weeks_last_year11

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~14.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv7.1.2
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases14.6
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?

69Good · 17% of overall
How it's scored
39.1/60Stars259 stars
13/25Forks37 forks
2.7/15Watchers4 watchers
Inputs used
forks37
stars259
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.4/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth28 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled28
top_contributor_share0.625
How it's scored
37.1/42Issue resolution88% of issues closed
19/30PR acceptance2,074/3,281 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 13/30 approved changesets -- score normalized to 4
Inputs used
merged_prs2,074
open_issues28
closed_issues211
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.883
closed_unmerged_prs1,207
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
17.1/25Owner reach237 followers of tolgee
23.1/25Track record47 public repos, account ~5 yr old
Inputs used
followers237
owner_typeOrganization
is_verified
owner_logintolgee
public_repos47
account_age_days1,991
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json, eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests14 out of 17 merged PRs checked by a CI test -- score normalized to 8
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://tolgee.io
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicslocalization, localization-tool, localization-management, internationalization, javascript, l10n, i18n
has_wikiyes
homepagehttps://tolgee.io
docs_sitehttps://tolgee.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests14 out of 17 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 13/30 approved changesets -- score normalized to 4
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
6/7.5Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
5/5Packagingpackaging workflow detected
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-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities262 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

79Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes701
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 config.eslintrc.json, eslint.config.js
11/11Static type checkinge2e/tsconfig.json, packages/core/tsconfig.json, packages/format-icu/tsconfig.json, packages/i18next/tsconfig.json, packages/ngx/tsconfig.json, packages/react/tsconfig.json, packages/svelte/tsconfig.json, packages/vue/tsconfig.json, packages/web/tsconfig.json, testapps/next-app-intl/tsconfig.json, testapps/next-app/tsconfig.json, testapps/next/tsconfig.json, testapps/ngx/tsconfig.json, testapps/react-i18next/tsconfig.json, testapps/react/tsconfig.json, testapps/svelte/tsconfig.json, testapps/vue-ssr/tsconfig.json, testapps/vue/tsconfig.json, tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
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
lockfilespackage-lock.json, pnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configse2e/tsconfig.json, packages/core/tsconfig.json, packages/format-icu/tsconfig.json, packages/i18next/tsconfig.json, packages/ngx/tsconfig.json, packages/react/tsconfig.json, packages/svelte/tsconfig.json, packages/vue/tsconfig.json, packages/web/tsconfig.json, testapps/next-app-intl/tsconfig.json, testapps/next-app/tsconfig.json, testapps/next/tsconfig.json, testapps/ngx/tsconfig.json, testapps/react-i18next/tsconfig.json, testapps/react/tsconfig.json, testapps/svelte/tsconfig.json, testapps/vue-ssr/tsconfig.json, testapps/vue/tsconfig.json, tsconfig.json
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
45/45Type-checkable codeTypeScript (statically typed)
54.9/55Manageable file sizes1/483 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes430,555
source_files_sampled483
oversized_source_files1
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

259GitHub stars
28contributors
29commits, last 12 months
3days since last push
100releases
1bus factor
28open issues
npmpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-18 16:15 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
8CI-Tests14 out of 17 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 13/30 approved changesets -- score normalized to 4
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
10Packagingpackaging workflow 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities262 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmcypress-real-events^1.13.0e2e/package.json
npmeslint^8.57.0e2e/package.json
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.13.0 — full methodology · metrics wiki.

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