Package Health/aaronholbrook/page-template-finder

aaronholbrook/page-template-finder

The package is tiny and easy to inspect, with an MIT declaration and no install-time scripts. Its only release was over 11 years ago, with no subsequent release activity, tests, or security policy, so maintenance risk is substantial.

Latest 0.1.0

Packagist

38%

Total Score

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, published over 11 years ago, with no releases in the last 12 months. That long period without updates is strong evidence of abandonment risk.

Package file tree

The package and repository each contain only three files: a README, composer manifest, and implementation file. This is easy to inspect, but it also provides little evidence of testing or mature project practices.

Repo package mention

The repository name matches the package, supporting the link, but its README does not mention the package name. That weakens repository-to-package traceability slightly.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no community signal to offset the lack of maintenance activity.

Repo tooling

Composer is used for builds, but no security scanning tools are present. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.