Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 07:47 UTC

ibexa / automated-translation

PHPCustom license★ 3 stars⑂ 7 forkssince Feb 2022View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ibexa/automated-translation holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (83/100) and lowest on AI Readiness (29/100). It was last updated today. 4 contributors account for most of its recent work.

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

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

Ownership

IbexaOrganization
40 followers98 public repossince May 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistibexa/automated-translationv5.0.93,1899819 days agotranslationnovactivedeeplgoogletranslateibexa

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9.7/36Commit cadence14/52 weeks with commits
13.1/18Commit volume28 commits in the last year
10/10OpenSSF Scorecard: Maintained16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year28
human_commit_share
days_since_last_push0
active_weeks_last_year14
How it's scored
16.2/27Ships releases98 version tags (no GitHub releases)
36/36Release recencylatest release 19 days ago
27/27Release cadencea release every ~38.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count98
latest_release_tagv5.0.9
releases_from_tagsyes
days_since_latest_release19
mean_days_between_releases38.2
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?

44Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
6.5/25Forks7 forks
6.5/15Watchers16 watchers
Inputs used
forks7
stars3
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
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
46.7/80Monthly downloads3,189 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesibexa/automated-translation
dependents1
ecosystemspackagist
total_downloads49,480
monthly_downloads3,189
unverified_packages_excluded

Sustainability & Governance

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

83Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
17.3/22.5Commit distributiontop contributor authored 23% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled19
top_contributor_share0.231
How it's scored
0/42Issue resolutionno issues or no data
25/30PR acceptance35/42 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 12/29 approved changesets -- score normalized to 4
Inputs used
merged_prs35
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs7
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
11.6/25Owner reach40 followers of ibexa
25/25Track record98 public repos, account ~6 yr old
Inputs used
followers40
owner_typeOrganization
is_verified
owner_loginibexa
public_repos98
account_age_days2,254
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 19 days ago
20/20Version history98 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesibexa/automated-translation
ecosystemspackagist
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
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
0/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsibexa-bundle, ibexa-product
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 12/29 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 9 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4/5SASTSAST tool is not run on all commits -- score normalized to 8
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.5
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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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
22/22Automated tests
11/11Lint / format config.php-cs-fixer.php, phpstan.neon
0/11Static type checking
0/10Reproducible environment
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
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
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
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/49 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes8,393
source_files_sampled49
oversized_source_files0

Key facts

3GitHub stars
19contributors
28commits, last 12 months
0days since last push
98releases
4bus factor
0open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 3 ★ / 0 ⇿
3Stars

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.

12233312024-112025-082026-05

Each point covers 2 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-07-21 07:47 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 12/29 approved changesets -- score normalized to 4
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained16 commit(s) and 0 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
8SASTSAST tool is not run on all commits -- score normalized to 8
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/guzzle^7.9composer.json
Packagistibexa/admin-ui~6.0.x-devcomposer.json
Packagistibexa/core~6.0.x-devcomposer.json
Packagistibexa/fieldtype-richtext~6.0.x-devcomposer.json
Packagistsymfony/console^7.4composer.json
Packagistsymfony/event-dispatcher^7.4composer.json
Packagistsymfony/form^7.4composer.json
Packagistsymfony/http-foundation^7.4composer.json
Packagistsymfony/routing^7.4composer.json
Packagistsymfony/yaml^7.4composer.json
All dependencies 34

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzledirect
Packagistibexa/admin-uidirect
Packagistibexa/coredirect
Packagistibexa/fieldtype-richtextdirect
Packagistsymfony/consoledirect
Packagistsymfony/event-dispatcherdirect
Packagistsymfony/formdirect
Packagistsymfony/http-foundationdirect
Packagistsymfony/routingdirect
Packagistsymfony/yamldirect
Packagistdg/bypass-finalsindirect
Packagistext-domindirect
Packagistext-libxmlindirect
Packagistibexa/calendarindirect
Packagistibexa/code-styleindirect
Packagistibexa/content-formsindirect
Packagistibexa/design-engineindirect
Packagistibexa/doctrine-schemaindirect
Packagistibexa/fieldtype-pageindirect
Packagistibexa/http-cacheindirect
Packagistibexa/migrationsindirect
Packagistibexa/notificationsindirect
Packagistibexa/rectorindirect
Packagistibexa/restindirect
Packagistibexa/searchindirect
Packagistibexa/twig-componentsindirect
Packagistibexa/userindirect
Packagistphpindirect
Packagistphpmd/phpmdindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpstan/phpstan-symfonyindirect
Packagistphpunit/phpunitindirect
Packagistsquizlabs/php_codesnifferindirect
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

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.17.0 — full methodology · metrics wiki.

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