dbisso/hooker

The small seven-file package has a clear license, README, and no install-time scripts, limiting packaging concerns. Its one-person project has no security policy or scanning, reducing confidence that future issues will receive timely review.

Latest v1.0.0

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about 10 years ago, with no releases in the last 12 months. That long-standing lack of updates is a meaningful abandonment concern, though the package may be intentionally stable.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, consistent with activity having stopped about 10 years ago. This is the strongest evidence of abandonment risk.

Maintainers

The registry lists one maintainer. A single maintainer is not inherently unhealthy, but combined with the decade-long lack of releases and commits it leaves limited visible maintenance capacity.

Project backing

The package and repository are owned by an individual rather than an organization. That is ordinary for a small project, but provides no visible organizational backup for its single maintainer.

Repo tooling

Composer build tooling is present, but no security scanning tooling was detected. That is a modest transparency and maintenance gap for a package with no recent activity.