larablocks/pigeon

Its tests, changelog, and README make the code easier to understand, while the organization-owned repository is still present. The lack of a security policy adds a smaller maintenance concern.

Latest 5.4.2

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in May 2017, and there have been no releases in the last 12 months. This long period without updates is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates sustained abandonment risk rather than a brief lull.

Repo issue activity

There were no new or closed issues or pull requests in the last month. With no recent commits, this is consistent with an inactive project rather than evidence of active maintenance.

Repo popularity

The repository has 14 stars and one fork, indicating limited adoption. Popularity is only supporting evidence, but these low counters provide little additional confidence in long-term maintenance.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap, especially for a package with no recent development activity.