neos/plim

Package file treedanger

The published tree contains private.key, certificate material, database backups, SQL dumps, and a JAR alongside application code. Including these operational and potentially sensitive files is a serious packaging hygiene concern.

Release historydanger

The package has only two releases, both in late 2015, with no release in nearly 11 years. This strongly indicates abandonment and outweighs the short six-day initial release interval.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in December 2015. There is no evidence of ongoing maintenance.

Lifecycle scriptscaution

The package runs post-create, post-install, and post-update Composer scripts. Install-time execution increases adoption risk, especially when the package is no longer actively maintained.

Maintainerscaution

Only one registry account has publishing access. A small maintainer base is not inherently unhealthy, but it offers little resilience for a project with no recent activity.