tomkyle/boilerplate-php

Its tests, release notes, and dependency checks provide useful maintenance evidence, while the single maintainer limits resilience. The long pause since the last release and absence of recent commits make continued upkeep uncertain, and all workflow actions are unpinned.

Latest 1.3.2

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

post-install-cmd and post-update-cmd scripts run during Composer installation or updates. These hooks are relevant to review because they execute automatically, although the package story identifies them as setup tooling rather than an unexplained runtime behavior.

Project backing

The package and repository are owned by the same individual account rather than an organization, so the single-person maintenance model is not buffered by visible organizational backing.

Release history

The package has 11 releases since January 2021, but none in the last 12 months; the latest release was about 15 months ago. This indicates a meaningful maintenance slowdown for a project intended as a reusable boilerplate.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this is evidence of currently inactive maintenance.

Security policy

No repository security policy was found. This is a minor transparency gap for reporting vulnerabilities, but it is not a severe dependency-health issue on its own.