alex-oliveira/ao-queue

The MIT license, matching repository, and practical README make the package transparent to adopt. No security policy or repository security scanning adds uncertainty around ongoing maintenance.

Latest 1.2.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in August 2018, and there were no releases in the last 12 months. This long release gap is strong evidence of abandonment risk despite the package having five historical releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for years.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no meaningful community signal to offset the stale maintenance record.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. The build setup is clear, while the lack of scanning modestly weakens maintenance hygiene.

Security policy

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