studionoir/translingua

Translingua 1.0.4 has a coherent, transparently linked source repository, an organization owner, a stable release version, recent repository activity, two active contributors, a changelog, and no deprecation or install-time lifecycle scripts. However, the project is only 3 days old with just 5 releases, has no tests in either the artifact or repository, and lacks a security policy and security-scanning tooling. It is reasonable to evaluate for adoption, but its short history and limited validation evidence warrant caution until it demonstrates longer-term maintenance and stronger project hygiene.

Latest 1.0.4

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package includes a substantial README and changelog, and the repository also has a changelog, but neither the artifact nor repository contains tests. For a CMS plugin with translation and content-handling behavior, the absence of tests is a meaningful validation gap.

Release history

The package is only 3 days old, despite having 5 releases in that period. This shows active initial publishing but provides almost no evidence of long-term maintenance stability.

Repo commit activity

Two commits and two active maintainers were recorded over the last 3 months. Both contributors are active, but the small absolute history reflects the package's very recent creation and leaves maintenance durability unproven.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a hygiene gap, though it is not by itself evidence of abandonment.

Security policy

The repository has no security policy. For a plugin that can process CMS content and call external AI translation services, the missing disclosure guidance is a meaningful transparency gap.