burriko/job-queue

Release historydanger

The package has had only one release, published about 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, despite the repository remaining available.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, while its last push was about 10 years ago. This confirms that the long release gap reflects stalled maintenance.

Repo popularitycaution

The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these numbers provide no community-maintenance cushion for the stale project.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools are present. The missing scanning is a modest transparency gap, while the established package tooling provides some baseline structure.

Version stabilitycaution

Version 0.1.0 is pre-1.0 and the README says the API may change regularly until v1. That limits maturity and compatibility confidence for adopters.