Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-25 01:18 UTC

loccy-dev / monorepo

Modern i18n tools for React & Vue

TypeScript · JavaScriptMIT★ 13 stars⑂ 1 forksince Jul 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

loccy-dev/monorepo holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on AI Readiness (64/100) and lowest on Vitality (29/100). It was last updated 14 days ago. A single contributor accounts for most of its recent work.

38
overall / 100
Weak

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.

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

Ownership

LoccyOrganization
1 follower1 public reposince Feb 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@loccy-dev/lint0.1.44,616531 days agoi18nl10nlinttranslationsreact-i18nextnext-intlvue-i18n

Metrics by category

Vitality

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

29At Risk · 21% of overall
How it's scored
28.8/36Push recency — last push 14 days ago
4.8/36Commit cadence — 7/52 weeks with commits
14.8/18Commit volume — 43 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year43
human_commit_share1
days_since_last_push14
active_weeks_last_year7
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

47Weak · 17% of overall
How it's scored
17.5/60Stars — 13 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars13
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
48.9/80Monthly downloads — 4,616 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@loccy-dev/lint
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads4,616
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?

48Weak · 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
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
23.4/42Issue resolution — 56% of issues closed
30/30PR acceptance — 1/1 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_prs1
open_issues4
closed_issues5
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.556
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
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of loccy-dev
5.3/25Track record — 1 public repos, account ~1 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginloccy-dev
public_repos1
account_age_days575

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 31 days ago
20/20Version history — 5 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@loccy-dev/lint
ecosystemsnpm
any_deprecatedno
min_days_since_publish31

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://loccy.dev
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsi18n, i18next, linters, next-intl, vue-i18n
has_wikino
homepagehttps://loccy.dev
docs_sitehttps://loccy.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

31At Risk · 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 — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
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/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
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 was created within the last 90 days. Please review its contents carefully
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 144 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages18
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:@loccy-dev/lint@0.1.4 runtime dependency closure — what installing the published package pulls in — 18 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.

64Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://loccy.dev/llms.txt)
11.2/40Legible commit history — 9 of 43 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://loccy.dev/llms.txt
legible_history_share0.209
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, apps/lint/Makefile
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — apps/claude-plugin/tsconfig.json, apps/extension/src/tests/test-projects/next-intl/tsconfig.json, apps/extension/src/tests/test-projects/react-i18next/tsconfig.json, apps/extension/src/tests/test-projects/vue-i18n/tsconfig.json, apps/extension/tsconfig.json, apps/lint/tsconfig.json, packages/node-platform/tsconfig.json, packages/shared/tsconfig.json, packages/types/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 43
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, apps/lint/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsapps/claude-plugin/tsconfig.json, apps/extension/src/tests/test-projects/next-intl/tsconfig.json, apps/extension/src/tests/test-projects/react-i18next/tsconfig.json, apps/extension/src/tests/test-projects/vue-i18n/tsconfig.json, apps/extension/tsconfig.json, apps/lint/tsconfig.json, packages/node-platform/tsconfig.json, packages/shared/tsconfig.json, packages/types/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.8/55Manageable file sizes — 1/309 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes75,644
source_files_sampled309
oversized_source_files1

Key facts

13GitHub stars
1contributors
43commits, last 12 months
14days since last push
0releases
1bus factor
4open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'loccy' from its registry
  • Could not fetch npm package '@repo/types' from its registry
  • Could not fetch npm package '@repo/shared' from its registry
  • Could not fetch npm package '@repo/node-platform' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 1.4 / 10
1.4aggregate

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-09-25 01:18 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/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities144 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
npm@babel/parser^7.29.2apps/extension/package.json
npm@babel/traverse^7.29.0apps/extension/package.json
npm@repo/sharedworkspace:^apps/extension/package.json
npm@repo/typesworkspace:^apps/extension/package.json
npm@vue/compiler-dom^3.5.32apps/extension/package.json
npm@vue/compiler-sfc^3.5.32apps/extension/package.json
npmdiff^9.0.0apps/extension/package.json
npmjson5^2.2.3apps/extension/package.json
npmlodash^4.18.1apps/extension/package.json
npmstring-similarity-js^2.1.4apps/extension/package.json
npmstrip-json-comments^5.0.3apps/extension/package.json
npmtypescript6.0.3apps/extension/package.json
npmchalk^5.6.2apps/lint/package.json
npmcommander^14.0.3apps/lint/package.json
npmora^9.3.0apps/lint/package.json
npm@repo/typesworkspace:*packages/node-platform/package.json
npmglobby^16.2.0packages/node-platform/package.json
npm@repo/typesworkspace:*packages/shared/package.json
npmignore^7.0.5packages/shared/package.json
npmjs-yaml^4.1.1packages/shared/package.json
npmjson5^2.2.3packages/shared/package.json
npmlodash-es^4.17.21packages/shared/package.json
npmpathe^2.0.3packages/shared/package.json
npmpicomatch^4.0.5packages/shared/package.json
npmphp-parser^3.7.0packages/shared/package.json
npmregex^6.1.0packages/shared/package.json
npmzod^3.24.0packages/shared/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

Dependency advisories 0

Installing npm:@loccy-dev/lint@0.1.4 pulls in 18 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.