tonydeng/tcp4p

Risky to adopt: the package has had no release or repository activity for nearly 10 years, leaving maintenance and compatibility concerns. It is clearly licensed, documented, and not deprecated or archived, but those positives do not offset the prolonged inactivity.

Latest 1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in March 2016, with no releases in the last 12 months; the nearly 10-year release gap is a strong abandonment concern.

Repo commit activity

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for nearly 10 years.

Maintainers

A single registry maintainer is consistent with a small user-owned project, but it leaves little visible maintainer capacity to address defects or compatibility issues.

Repo tooling

Composer is used for the build, providing basic project tooling, but no security scanning tools are configured to add assurance.

Repository archived

The repository is not archived, which is a positive counter-signal, but its last push was nearly 10 years ago and therefore does not demonstrate current maintenance.