Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-28 09:55 UTC

Locastic / ApiPlatformTranslationBundle

Translation bundle for ApiPlatform based on Sylius translation

PHPMIT★ 84 stars⑂ 30 forkssince Sep 2018View on GitHub ↗

Locastic/ApiPlatformTranslationBundle holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (69/100) and lowest on AI Readiness (36/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

LocasticOrganization
15 followers36 public repossince Sep 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistlocastic/api-platform-translation-bundlev2.0.13,8741920 days ago

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
2.1/36Commit cadence — 3/52 weeks with commits
10.6/18Commit volume — 14 commits in the last year
10/10OpenSSF Scorecard: Maintained — 14 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year14
human_commit_share1
days_since_last_push0
active_weeks_last_year3
How it's scored
27/27Ships releases — 17 releases published
36/36Release recency — latest release 20 days ago
12.6/27Release cadence — a release every ~259 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count17
latest_release_tagv2.0.1
releases_from_tagsno
days_since_latest_release20
mean_days_between_releases259
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?

58Moderate · 17% of overall
How it's scored
31.1/60Stars — 84 stars
12.2/25Forks — 30 forks
4.7/15Watchers — 8 watchers
Inputs used
forks30
stars84
watchers8
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
47.8/80Monthly downloads — 3,874 downloads/month across packagist
0/20Registry dependents — 0 packages depend on it
Inputs used
packageslocastic/api-platform-translation-bundle
dependents0
ecosystemspackagist
total_downloads479,428
monthly_downloads3,874

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.5/22.5Commit distribution — top contributor authored 58% of commits
13.5/13.5Contributor breadth — 21 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.579
How it's scored
36.8/42Issue resolution — 88% of issues closed
26.8/30PR acceptance — 42/47 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 13/29 approved changesets -- score normalized to 4
Inputs used
merged_prs42
open_issues5
closed_issues35
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.875
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 backing — organization-owned
0/20Verified domain
8.7/25Owner reach — 15 followers of Locastic
23.4/25Track record — 36 public repos, account ~12 yr old
Inputs used
followers15
owner_typeOrganization
is_verified
owner_loginLocastic
public_repos36
account_age_days4,708

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 20 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslocastic/api-platform-translation-bundle
ecosystemspackagist
any_deprecatedno
min_days_since_publish20

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.dist.php
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 14 out of 29 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1/2.5CI-Tests — 14 out of 29 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 13/29 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 14 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 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): packaging, 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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29.5/40Legible commit history — 42 of 76 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.553
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 76
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/29 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes10,161
source_files_sampled29
oversized_source_files0

Key facts

84GitHub stars
21contributors
14commits, last 12 months
0days since last push
17releases
1bus factor
5open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 30 ⇿
0Stars
30Forks
14Releases

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.

0510152025303032018-092022-042025-12
Major 0Minor 0Patch 9

Each point covers 7 days.

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-28 09:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests14 out of 29 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 13/29 approved changesets -- score normalized to 4
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 5 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
Packagistapi-platform/symfony^3.4 || ^4.0composer.json
Packagistdoctrine/orm^3.0composer.json
Packagistdoctrine/doctrine-bundle^2.13 || ^3.0composer.json
Packagistsymfony/config^6.4 || ^7.0 || ^8.0composer.json
Packagistsymfony/dependency-injection^6.4 || ^7.0 || ^8.0composer.json
Packagistsymfony/deprecation-contracts^2.5 || ^3.0composer.json
Packagistsymfony/http-kernel^6.4 || ^7.0 || ^8.0composer.json
Packagistsymfony/translation^6.4 || ^7.0 || ^8.0composer.json
All dependencies 18

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

RegistryPackageVersionRelation
Packagistapi-platform/symfonydirect
Packagistdoctrine/doctrine-bundledirect
Packagistdoctrine/ormdirect
Packagistsymfony/configdirect
Packagistsymfony/dependency-injectiondirect
Packagistsymfony/deprecation-contractsdirect
Packagistsymfony/http-kerneldirect
Packagistsymfony/translationdirect
Packagistapi-platform/coreindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistphpindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-doctrineindirect
Packagistphpstan/phpstan-symfonyindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/framework-bundleindirect
Packagistsymfony/validatorindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

Raw JSON report machine-readable

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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