clean/repository

Release historydanger

The package has had no release in nearly nine years: its latest release was August 2017, despite nine releases overall. This is strong evidence of prolonged maintenance inactivity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing that development is currently inactive.

Repo toolingcaution

Composer is used for the build, but no security-scanning tools were detected. This is a modest transparency and hygiene gap, not a standalone reason to reject the package.

Repository archivedcaution

The repository is not archived and was last pushed in November 2019, which is better than an explicitly abandoned repository but does not offset the long release and commit gap.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency, although the absence is less significant than the demonstrated maintenance inactivity.