shawngiroux/php_tui

The codebase is very small and lacks a README, tests, and a security policy, limiting confidence for a library. MIT licensing and a minimal dependency profile reduce friction, but do not offset the maintenance gap.

Latest v0.1-alpha

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 5 years and 11 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the old last push, this materially increases abandonment risk.

Package file tree

The artifact and repository each contain only five files, including two classes and examples. This may reflect a deliberately small library, but it provides little evidence of mature project structure.

Package scaffolding

The package has no README, tests, or changelog; absent tests and changelog are normal in published artifacts, but the missing README makes a small library harder to understand and adopt. A GitHub release exists for this version, providing some release visibility despite having no notes.

Repo tooling

Composer is used for builds, which is appropriate for the package, but no security scanning tooling was detected. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.