owenmelbz/php-to-pot

The MIT license, focused four-file CLI, and modest dependency set keep adoption straightforward. Its maintenance record is too thin for a dependable long-term dependency, especially with no tests or security tooling.

Latest 0.0.3

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Health Score Breakdown

Release history

The package has made no release in more than 8 years: all 3 releases date to March 2018, with none in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history's long inactivity. The repository is not archived, but that does not compensate for the absence of recent work.

Package scaffolding

The artifact includes a README, which helps consumers use this focused command-line tool, while missing tests and a changelog are normal for published artifacts. However, the repository also has no tests, reducing confidence in future maintenance or changes.

Repo popularity

The repository has 0 stars, forks, and watchers, providing no supporting evidence of community use or review. Popularity is only supporting evidence, so this reinforces rather than determines the overall concern.

Repo tooling

Composer is used for the build, but the repository has no security scanning tools. For a small CLI this is a hygiene gap rather than a standalone adoption blocker, though it adds to the weak maintenance picture.