pop-backbone/php-hooks

This is a generally healthy, actively maintained dependency: it has 145 releases over roughly 3 years and 33 releases in the last 12 months, the current version is a stable non-prerelease, the registry does not mark it deprecated, and the linked organization-owned repository is active and correctly associated with the package. The main concerns are a single active maintainer and complete concentration of recent commits, very limited repository popularity, no tests or changelog, and no security scanning or security policy. The package is small and its README documents its forked origin and monorepo development location, which reduces the significance of some scaffolding gaps, but adoption still carries moderate maintainer-continuity and transparency risk.

Latest 19.2.4

Packagist

78%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a minor operational concentration concern, although the organization-owned repository provides some project-level backing.

Package scaffolding

A substantial README is present and explains the fork and development location, but neither the artifact nor repository contains tests or a changelog. For a small library this is a genuine, though not severe, maintenance-transparency gap.

Repo bus factor

All 13 recent commits came from one contributor, creating a real continuity risk if that maintainer becomes unavailable. The organization ownership partially offsets the risk by providing a potential handoff path.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, indicating limited external adoption. Popularity is supporting evidence rather than a decisive health measure, so this is caution rather than danger.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The absence of scanning lowers assurance, although it is not by itself evidence of abandonment.