filipekp/queue

This release is usable but carries meaningful maintenance and transparency concerns. The package has a long history, 75 releases, a stable non-prerelease version, recent publication, and a matching non-archived repository, which are positive signs. However, the repository has had no commits or active maintainers in the last 3 months, contains no tests or changelog, has no security policy or scanning tooling, and is controlled by a single registry maintainer. The declared proprietary license is also a significant concern for adopting it as an open-source dependency. Overall, it is not deprecated or abandoned outright, but the limited engineering evidence and licensing position warrant caution before depending on it.

Latest v2.1.11

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

The package declares a proprietary license and has no license file, which limits transparency and may impose restrictions on redistribution or use as an open-source dependency.

Maintainers

Only one account has registry publish access. The linked repository is owned by the corresponding individual user, so there is no organization backing signal to compensate for the narrow maintainer base.

Package scaffolding

A README is present, but it is only 58 characters and both the artifact and repository lack tests and a changelog; the repository's GitHub Releases provide some release-process compensation, but coverage remains thin.

Project backing

The repository is owned by an individual user rather than an organization, offering limited visible project backing; this reinforces the risk from the single registry maintainer.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last 3 months. This materially weakens evidence of current maintenance, despite the recent registry release and repository push.