bangsamu/library-clay

This is a usable, actively released Composer package with 50 releases over roughly 3 years, 21 releases in the last 12 months, a stable non-prerelease version, an MIT license, and no registry deprecation or install-time lifecycle scripts. However, the linked user-owned repository shows no commits or active maintainers in the last 3 months, has no tests, changelog, security policy, or security-scanning tooling, and has negligible adoption signals. The coherent 16-file package tree and matching repository provide some transparency, but the thin validation and security processes make this a caution-level dependency rather than a strongly mature one.

Latest v1.0.47

Packagist

66%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months. This conflicts with the strong registry release cadence and raises concern that releases may not reflect sustained source-level maintenance.

Maintainers

Only one registry publishing account is listed. The repository is user-owned rather than organization-owned, so there is limited visible publishing redundancy and some bus-factor concern.

Package scaffolding

A README is present, but it is only 61 characters and both the artifact and repository lack tests and a changelog. For a framework package containing controllers, services, middleware, and routes, the absence of tests is a meaningful maintenance and regression risk.

Project backing

The repository owner is a user account, not an organization, so there is no organizational backing signal to compensate for the single publisher or thin contributor evidence.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not inherently negative, but it provides no evidence of an active feedback or review process.