Package Health/hardcodear/api-response-service

hardcodear/api-response-service

This is a usable, transparently licensed package with a stable v2.0.0 release, five releases in the last 12 months, a matching repository, repository tests, and no deprecation or archival indicators. The main concern is maintenance continuity: the repository recorded zero commits and zero active maintainers over the last 3 months despite a recent release and push, while the project has very low adoption and lacks a security policy and explicit workflow token permissions. It is reasonable to evaluate for adoption, but dependency owners should verify continued maintainer responsiveness and monitor future releases.

Latest v2.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Maintainers

Only one registry account has publish access, leaving limited publishing redundancy; this is a modest continuity concern for a user-owned project.

Project backing

The repository is owned by a user account rather than an organization, so there is no organizational backing signal to offset the single-publisher and single-owner continuity concerns.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, which is a concrete warning about current maintenance continuity despite the recent release and push timestamps.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. Low popularity is not disqualifying, but it provides little external evidence of adoption or community support.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured, leaving a security-hygiene gap without making the package unfit to depend on.