lambdaphp/installer

Release historydanger

The latest release was published in May 2019, nearly 7 years ago, and there have been no releases in the last 12 months. That long gap is strong evidence of abandonment risk.

Licensecaution

The manifest declares MIT, while the artifact license file is detected as GPL-3.0. The package is licensed, but the mismatch creates a material legal and transparency concern.

Maintainerscaution

Only one registry account has publish access, and the repository owner is an individual rather than an organization. This leaves limited visible publishing redundancy, although access records alone do not prove maintenance activity.

Repo popularitycaution

The repository has 4 stars, 0 forks, and 1 watcher, providing little supporting evidence of active community use or review. Popularity is only supporting evidence, so this is not decisive by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious than the maintenance concerns.