michabbb/toper

Release historydanger

The package has had only two releases, with none in the last 12 months, and its latest release was about six years ago. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the latest push being about six years ago. No provided maintenance signal compensates for this inactivity.

Repo toolingcaution

Composer and Phing provide build tooling, but the repository has no security scanning tools. That is a modest transparency and maintenance gap for an old dependency.

Security policycaution

The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This matters more because the project also shows prolonged inactivity.

Version stabilitycaution

The latest version is v0.1.1 and is not a stable major release, so the package remains early-version software despite its age. This compounds the concern created by its inactive release history.