cracksalad/i18n

Clear licensing, a useful README, release notes, and Psalm scanning support a transparent small library. The workflow’s high-confidence unpinned container image is a hygiene risk, while its single-maintainer ownership limits resilience.

Latest 0.1.2

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is listed, and the repository is owned by the same individual rather than an organization. That creates a thin maintainer base and limited continuity if the maintainer stops contributing.

Project backing

The registry namespace and repository are owned by the same individual user, with no organization backing shown. This supports the thin-maintainer assessment rather than compensating for it.

Release history

Only two releases have been published, with the latest on July 13, 2024 and none in the following 12 months; this indicates weak ongoing maintenance for a package still marked 0.1.2.

Repo commit activity

There were no commits and no active maintainers in the past three months. Combined with the old latest release, this is meaningful evidence of inactivity.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is neutral for a small package, but it provides no evidence of active project engagement.