Package Health/abuseio/abuseio-installer

abuseio/abuseio-installer

The package has clear MIT licensing, a substantial README, and no install-time scripts. Its source and release activity stopped in 2019, while the assessed 6.0.1 release is newer than the recorded latest 5.0.2; the repository also lacks security scanning and a security policy.

Latest 6.0.1

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than seven years, with the last recorded release on April 3, 2019, despite 23 historical releases. This is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the package having been inactive for years. This materially increases maintenance and abandonment risk.

Repo package mention

The repository name matches the package, reducing the risk of an unrelated repository, but the README does not mention this package name and instead presents another package identity. That mismatch warrants caution.

Repo tooling

The repository uses Composer, showing basic build tooling, but has no security scanning configured. For an installer that handles application setup and environment configuration, that is a meaningful hygiene gap.

Repository archived

The repository is not archived, which is a compensating ownership signal, but its last push was in June 2019 and does not offset the long inactivity shown elsewhere.