gettext/json

The MIT license, clear README, repository tests, and small dependency set support straightforward adoption. GitHub Actions uses all three actions without pinning, and no security policy or scanning is present.

Latest v1.0.1

Packagist

57%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about five years ago, with no releases in the last 12 months and only two releases overall. This is the strongest evidence of reduced maintenance, although the package remains stable and is not deprecated.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. This raises abandonment risk even though the repository is not archived.

Repo popularity

The repository has 6 stars and 2 forks, indicating a small user and contributor footprint. Popularity is supporting evidence rather than a verdict, but it offers little evidence of broad ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk by itself.

Workflow audit

The sole workflow was fully analyzed with no dangerous triggers or audit findings, but all 3 of 3 action references are unpinned. That leaves avoidable build reproducibility and action-supply-chain exposure.