lesname/queue

This release appears suitable to depend on, with strong evidence of ongoing maintenance and reasonable package hygiene: it has 36 releases over roughly 4 years and 6 releases in the last 12 months, the repository is not archived, and it was pushed recently. The main concerns are that all 12 commits in the last 3 months came from one contributor, the repository has no security policy or security-scanning tooling, and repository popularity is very low. These are meaningful resilience and transparency gaps, but they are partly offset by organization ownership, active release and pull-request activity, repository tests, a valid MIT license, read-only workflow permissions, and no dangerous workflow patterns.

Latest 0.9.4

Packagist

79%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all 12 commits in the last 3 months, creating a significant continuity risk; organization ownership provides some ability to hand maintenance off but does not demonstrate a second active contributor.

Repo commit activity

The repository recorded 12 commits in the last 3 months, showing active work, but all were produced by one active maintainer.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher; this provides little external adoption evidence, though popularity is supporting evidence rather than a health verdict.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected, leaving a security-process gap.

Security policy

The repository has no security policy, which weakens vulnerability-reporting transparency and response expectations.