crustum/batch-queue

The package is licensed, documented, and backed by a repository with tests. Its small release history, absent security tooling, and unpinned workflow actions limit confidence in long-term maintenance and build hygiene.

Latest 1.1.0

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is young at 287 days with four releases, all within the last 12 months; the short history and bursty cadence provide limited evidence of mature maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Although the repository was pushed recently and the package has only four releases, this is a meaningful sign of currently quiet maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but the package is young and popularity alone does not establish a health problem.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That leaves an avoidable gap in repository transparency and automated supply-chain hygiene.

Security policy

The repository has no security policy. This is a maintenance and disclosure gap, though it is not severe enough on its own to make the release unfit.