Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 10:54 UTC

Laravel-Lang / status-generator

Translation status generator for Laravel Lang projects.

PHPMIT★ 4 stars⑂ 3 forkssince Sep 2021View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

Laravel-Lang/status-generator holds a health index of 32 out of 100, placing it in the At Risk band. It scores highest on Vitality (67/100) and lowest on Security (42/100). It was last updated 62 days ago. A single contributor accounts for most of its recent work.

32
overall / 100
At Risk

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.

32
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 59 is calibrated to 63 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Laravel LangOrganization
167 followers24 public repossince Jul 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistlaravel-lang/status-generator2.16.022,1698067 days agogeneratorlaravellanguageslaravel-lang

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
18/36Push recencylast push 62 days ago
9/36Commit cadence13/52 weeks with commits
15.4/18Commit volume51 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year51
human_commit_share0.93
days_since_last_push62
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases80 releases published
36/36Release recencylatest release 67 days ago
27/27Release cadencea release every ~39.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count80
latest_release_tag2.16.0
releases_from_tagsno
days_since_latest_release67
mean_days_between_releases39.7
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?

50Moderate · 17% of overall
How it's scored
7.7/60Stars4 stars
2.5/25Forks3 forks
0/15Watchers2 watchers
Inputs used
forks3
stars4
watchers2
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
57.9/80Monthly downloads22,169 downloads/month across packagist
6.9/20Registry dependents10 packages depend on it
Inputs used
packageslaravel-lang/status-generator
dependents10
ecosystemspackagist
total_downloads1,911,192
monthly_downloads22,169
unverified_packages_excluded

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
2.7/22.5Commit distributiontop contributor authored 88% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.881
How it's scored
0/42Issue resolutionno issues or no data
29.7/30PR acceptance113/114 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/12 approved changesets -- score normalized to 0
Inputs used
merged_prs113
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
16/25Owner reach167 followers of Laravel-Lang
22.2/25Track record24 public repos, account ~6 yr old
Inputs used
followers167
owner_typeOrganization
is_verified
owner_loginLaravel-Lang
public_repos24
account_age_days2,216
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 packagist
35/35Publish recencylatest publish 67 days ago
20/20Version history80 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageslaravel-lang/status-generator
ecosystemspackagist
any_deprecatedno
min_days_since_publish67

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests9 out of 16 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://laravel-lang.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://laravel-lang.com
docs_sitehttps://laravel-lang.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.2/2.5CI-Tests9 out of 16 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/12 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 10 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.5
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier27
security_posture_before_jurisdiction54
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages9
unassessed_packages16
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 9 resolved dependencies against OSV. 16 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://laravel-lang.com/llms.txt)
22.9/40Legible commit history40 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://laravel-lang.com/llms.txt
legible_history_share0.43
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.03
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/149 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes7,108
source_files_sampled149
oversized_source_files0

Key facts

4GitHub stars
3contributors
51commits, last 12 months
62days since last push
80releases
1bus factor
0open issues
Packagistpackage 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.

12233312023-082024-122026-05
Major 1Minor 15Patch 20

Each point covers 3 days.

OpenSSF Scorecard 5.5 / 10
5.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-08-22 10:54 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests9 out of 16 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/12 approved changesets -- score normalized to 0
10Contributorsproject has 10 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Packagistarchtechx/enums^0.3.2 || ^1.0composer.json
Packagistdeeplcom/deepl-php^1.5composer.json
Packagistdragon-code/pretty-array^4.0composer.json
Packagistdragon-code/support^6.11composer.json
Packagistguzzlehttp/guzzle^7.4composer.json
Packagistilluminate/console^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/container^10.0 || ^11.0 || ^12.0 || ^13.0composer.json
Packagistlaravel-lang/locale-list^1.2composer.json
Packagiststichoza/google-translate-php^5.1composer.json
Packagistsymfony/console^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/finder^6.0 || ^7.0 || ^8.0composer.json
All dependencies 25

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

RegistryPackageVersionRelation
Packagistarchtechx/enumsdirect
Packagistdeeplcom/deepl-phpdirect
Packagistdragon-code/pretty-arraydirect
Packagistdragon-code/supportdirect
Packagistguzzlehttp/guzzledirect
Packagistilluminate/consoledirect
Packagistilluminate/containerdirect
Packagistlaravel-lang/locale-listdirect
Packagiststichoza/google-translate-phpdirect
Packagistsymfony/consoledirect
Packagistsymfony/finderdirect
npm@biomejs/biome2.2.2indirect
npm@biomejs/cli-darwin-arm642.2.2indirect
npm@biomejs/cli-darwin-x642.2.2indirect
npm@biomejs/cli-linux-arm642.2.2indirect
npm@biomejs/cli-linux-arm64-musl2.2.2indirect
npm@biomejs/cli-linux-x642.2.2indirect
npm@biomejs/cli-linux-x64-musl2.2.2indirect
npm@biomejs/cli-win32-arm642.2.2indirect
npm@biomejs/cli-win32-x642.2.2indirect
Packagistext-jsonindirect
Packagistext-zipindirect
Packagistphpindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/var-dumperindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 9 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 16 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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