Package Health/ryunosuke/utility-attribute

ryunosuke/utility-attribute

Usable with caveats: the package is stable, licensed, documented, and backed by a matching repository with tests. However, it has had no release in about 15 months and no commits in the last 3 months, with only one maintainer, so maintenance continuity is uncertain.

Latest v1.1.3

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing account is listed, and the repository is user-owned rather than organization-backed. This creates limited maintainer redundancy if the primary maintainer becomes unavailable.

Release history

The package has 7 releases over about 31 months, but none in the last 12 months and the latest release was about 15 months ago. This indicates a meaningful maintenance slowdown, although the existing release history shows it was previously maintained.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. For a small library this may reflect stability, but combined with no release in about 15 months it leaves maintenance continuity uncertain.

Repo tooling

The repository uses Composer, which is appropriate for this PHP package, but no security scanning tool is configured. The missing scanner is a transparency gap rather than evidence that the package is unsafe.

Repository archived

The linked repository is not archived, but its last push was about 15 months ago. The active repository status is positive, while the old last-push date is consistent with the maintenance concern from release history.