neos/limp

Package file treedanger

The published tree includes private.key, certificate material, database backups, and SQL files alongside application code. Even if these are development artifacts, their inclusion indicates weak release hygiene.

Release historydanger

The package has only two releases, both in 2015, and none in the last 11 years. That sustained inactivity is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the release history showing no current maintenance.

Licensecaution

The manifest declares MIT, but the README says the project is licensed under Creative Commons and no license file was detected. The conflicting licensing evidence creates a real adoption and transparency concern.

Lifecycle scriptscaution

The package defines post-create, post-install, and post-update Composer scripts, so installation can execute project code. This is not inherently unsafe, but it increases the maintenance and review burden for an otherwise stale package.