gettext/translator

Clear documentation, licensing, tests in the repository, and a small runtime dependency keep adoption straightforward. The workflow uses three unpinned actions and the project has no security policy, so maintenance and build hygiene deserve attention.

Latest v1.2.3

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 6 years and has two releases in the last 12 months, but its median release interval is about 14 months, indicating a slow maintenance cadence.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months. The recent release and push provide some compensating evidence, but current development activity remains quiet.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.

Security policy

The repository has no security policy. This does not show a vulnerability, but it reduces transparency about how dependency issues and reports are handled.

Workflow audit

The sole workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but all three action references are unpinned, leaving them exposed to upstream changes.