flipboxdigital/queue

Documentation, a detected MIT license, and a correctly matching organization-backed repository provide useful transparency. The lack of repository security tooling and a security policy adds modest risk for a package handling queued work.

Latest 1.0.0-beta.3

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in August 2017, with no releases in the last nine years. That long silence is strong evidence of abandonment for a package used in application infrastructure.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases. The repository is not archived, but it shows no current development activity.

Repo issue activity

There were no new or closed issues or pull requests in the last month. With no recent commits or releases, this supports the conclusion that the project is inactive rather than simply quiet in issue tracking.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is visible while automated security coverage is limited.

Security policy

The linked repository has no security policy. This is a transparency gap for a package that may process application jobs, although it does not by itself show an unsafe release.