mix/delayer-client

Its small dependency footprint and tested, licensed artifact reduce adoption friction. The organization-owned repository remains unarchived, but no recent release or commit activity limits confidence in ongoing support.

Latest v1.0.3

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in April 2019, with no releases in the last 12 months, indicating a long period without published maintenance. The three-release history shows the package is established but not actively evolving.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with the repository having had no push for over five years. This materially raises abandonment risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month and no open items, offering no evidence of current community or maintainer activity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small package this is a hygiene gap rather than a severe dependency risk.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.