Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 20:42 UTC

bicstone / ra-language-japanese

Japanese messages for react-admin

TypeScriptMIT★ 32 stars⑂ 6 forkssince Nov 2019View on GitHub ↗

bicstone/ra-language-japanese holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on AI Readiness (46/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Oishi TakanoriPersonal account
38 followers12 public repossince Feb 2019@Findy

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@bicstone/ra-language-japanese5.15.016,77048102 days agoadmin-on-restreactreact-admintranslationi18njapanese

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 143 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year143
human_commit_share0.05
days_since_last_push0
active_weeks_last_year51
How it's scored
27/27Ships releases — 48 releases published
27/36Release recency — latest release 102 days ago
19.8/27Release cadence — a release every ~57.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count48
latest_release_tagv5.15.0
releases_from_tagsno
days_since_latest_release102
mean_days_between_releases57.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?

59Moderate · 17% of overall
How it's scored
24.2/60Stars — 32 stars
5.8/25Forks — 6 forks
0/15Watchers — 1 watchers
Inputs used
forks6
stars32
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
56.3/80Monthly downloads — 16,770 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@bicstone/ra-language-japanese
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads16,770
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.5/22.5Commit distribution — top contributor authored 98% 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.98
How it's scored
33.6/42Issue resolution — 80% of issues closed
28.3/30PR acceptance — 540/572 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs540
open_issues2
closed_issues8
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.8
closed_unmerged_prs32
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
11.4/25Owner reach — 38 followers of bicstone
20.1/25Track record — 12 public repos, account ~7 yr old
Inputs used
followers38
owner_typeUser
is_verified—
owner_loginbicstone
public_repos12
account_age_days2,828
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 102 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@bicstone/ra-language-japanese
ecosystemsnpm
any_deprecatedno
min_days_since_publish102

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/@bicstone/ra-language-japanese
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsreact-admin, admin-on-rest, react, hacktoberfest, japanese, japanese-language, i18n, translation
has_wikino
homepagehttps://www.npmjs.com/package/@bicstone/ra-language-japanese
docs_sitehttps://www.npmjs.com/package/@bicstone/ra-language-japanese
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

77Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/2 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
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.1
Excluded from scoring (no data or not applicable): 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_packages14
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:@bicstone/ra-language-japanese@5.15.0 runtime dependency closure — what installing the published package pulls in — 14 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
0/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 95 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.95
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes9,238
source_files_sampled2
oversized_source_files0

Key facts

32GitHub stars
3contributors
143commits, last 12 months
0days since last push
48releases
1bus factor
2open 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 ★ / 6 ⇿
0Stars
6Forks
38Releases

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.

123456612020-062023-012025-08
Major 2Minor 19Patch 8

Each point covers 5 days.

OpenSSF Scorecard 7.1 / 10
7.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-11-18 20:42 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests27 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/2 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmra-core^5.0.0package.json
All dependencies 182

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

RegistryPackageVersionRelation
npmra-core5.15.5direct
npm@andrewbranch/untar.js1.0.4indirect
npm@arethetypeswrong/cli0.18.5indirect
npm@arethetypeswrong/core0.18.5indirect
npm@babel/runtime7.24.7indirect
npm@babel/runtime7.29.7indirect
npm@biomejs/biome2.6.2indirect
npm@biomejs/cli-android-arm642.6.2indirect
npm@biomejs/cli-android-x642.6.2indirect
npm@biomejs/cli-darwin-arm642.6.2indirect
npm@biomejs/cli-darwin-x642.6.2indirect
npm@biomejs/cli-linux-arm642.6.2indirect
npm@biomejs/cli-linux-arm64-musl2.6.2indirect
npm@biomejs/cli-linux-x642.6.2indirect
npm@biomejs/cli-linux-x64-musl2.6.2indirect
npm@biomejs/cli-win32-arm642.6.2indirect
npm@biomejs/cli-win32-x642.6.2indirect
npm@braidai/lang1.1.2indirect
npm@colors/colors1.5.0indirect
npm@loaderkit/resolve1.0.6indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@publint/pack0.1.7indirect
npm@sindresorhus/is4.6.0indirect
npm@tanstack/query-core5.90.10indirect
npm@tanstack/react-query5.90.10indirect
npmajv8.20.0indirect
npmall-contributors-cli6.26.1indirect
npmansi-escapes4.3.2indirect
npmansi-escapes7.3.0indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmany-promise1.3.0indirect
npmarg5.0.2indirect
npmastral-regex2.0.0indirect
npmasync3.2.5indirect
npmbraces3.0.3indirect
npmcamelcase5.3.1indirect
npmchalk4.1.2indirect
npmchalk5.6.2indirect
npmchar-regex1.0.2indirect
npmchardet0.7.0indirect
npmcjs-module-lexer1.4.3indirect
npmcli-cursor3.1.0indirect
npmcli-highlight2.1.11indirect
npmcli-table30.6.5indirect
npmcli-width3.0.0indirect
npmcliui6.0.0indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommander10.0.1indirect
npmcookie1.1.1indirect
npmdate-fns3.6.0indirect
npmdecamelize1.2.0indirect
npmdecode-uri-component0.2.2indirect
npmdidyoumean1.2.2indirect
npmemoji-regex8.0.0indirect
npmemojilib2.4.0indirect
npmenvironment1.1.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp1.0.5indirect
npmeventemitter35.0.4indirect
npmexternal-editor3.1.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-glob3.3.3indirect
npmfast-uri3.1.5indirect
npmfastq1.20.1indirect
npmfflate0.8.3indirect
npmfigures3.2.0indirect
npmfill-range7.1.1indirect
npmfilter-obj1.1.0indirect
npmfind-up4.1.0indirect
npmget-caller-file2.0.5indirect
npmglob-parent5.1.2indirect
npmhas-flag4.0.0indirect
npmhighlight.js10.7.3indirect
npmiconv-lite0.4.24indirect
npminflection3.0.2indirect
npminquirer7.3.3indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmjs-tokens4.0.0indirect
npmjson-fixer1.6.15indirect
npmjson-schema-traverse1.0.0indirect
npmjsonexport3.2.0indirect
npmlocate-path5.0.0indirect
npmlodash4.18.1indirect
npmlodash.truncate4.4.2indirect
npmloose-envify1.4.0indirect
npmlru-cache11.5.2indirect
npmmarked9.1.6indirect
npmmarked-terminal7.3.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmmimic-fn2.1.0indirect
npmmri1.2.0indirect
npmmute-stream0.0.8indirect
npmmz2.7.0indirect
npmnode-emoji2.2.0indirect
npmnode-fetch2.7.0indirect
npmobject-assign4.1.1indirect
npmonetime5.1.2indirect
npmos-tmpdir1.0.2indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-try2.2.0indirect
npmpackage-manager-detector1.8.0indirect
npmparse55.1.1indirect
npmparse56.0.1indirect
npmparse5-htmlparser2-tree-adapter6.0.1indirect
npmpath-exists4.0.0indirect
npmpegjs0.10.0indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.2indirect
npmpify5.0.0indirect
npmprettier2.8.8indirect
npmprettier3.9.10indirect
npmpublint0.3.25indirect
npmquery-string7.1.3indirect
npmqueue-microtask1.2.3indirect
npmreact18.3.1indirect
npmreact-dom18.3.1indirect
npmreact-error-boundary4.1.2indirect
npmreact-hook-form7.83.0indirect
npmreact-is19.2.8indirect
npmreact-router7.18.2indirect
npmreact-router-dom7.18.2indirect
npmregenerator-runtime0.14.1indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmrequire-main-filename2.0.0indirect
npmrestore-cursor3.1.0indirect
npmreusify1.1.0indirect
npmrun-async2.4.1indirect
npmrun-parallel1.2.0indirect
npmrxjs6.6.7indirect
npmsade1.8.1indirect
npmsafer-buffer2.1.2indirect
npmscheduler0.23.2indirect
npmsemver7.8.5indirect
npmset-blocking2.0.0indirect
npmset-cookie-parser2.7.2indirect
npmsignal-exit3.0.7indirect
npmskin-tone2.0.0indirect
npmslice-ansi4.0.0indirect
npmsplit-on-first1.1.0indirect
npmstrict-uri-encode2.0.0indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmsupports-color7.2.0indirect
npmsupports-hyperlinks3.2.0indirect
npmtable6.9.0indirect
npmthenify3.3.1indirect
npmthenify-all1.6.0indirect
npmthrough2.3.8indirect
npmtinyexec1.3.0indirect
npmtmp0.0.33indirect
npmto-regex-range5.0.1indirect
npmtr460.0.3indirect
npmtslib1.14.1indirect
npmtype-fest0.21.3indirect
npmtypescript5.6.1-rcindirect
npmtypescript6.0.3indirect
npmunicode-emoji-modifier-base1.0.0indirect
npmvalidate-npm-package-name5.0.1indirect
npmwebidl-conversions3.0.1indirect
npmwhatwg-url5.0.0indirect
npmwhich-module2.0.1indirect
npmwrap-ansi6.2.0indirect
npmwrap-ansi7.0.0indirect
npmy18n4.0.3indirect
npmy18n5.0.8indirect
npmyargs15.4.1indirect
npmyargs16.2.2indirect
npmyargs-parser18.1.3indirect
npmyargs-parser20.2.9indirect
npmzshy0.8.1indirect
Dependency advisories 0

Installing npm:@bicstone/ra-language-japanese@5.15.0 pulls in 14 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.