bcc/resque-bundle

The README, MIT declaration, and small runtime dependency set make the package understandable to adopt. Its source repository is unarchived and still identifies the package, but maintenance evidence is too old for a dependable current dependency.

Latest 1.1.7

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published on June 4, 2013, and there have been no releases in the last 12 months. This long publication gap is strong evidence of abandonment risk.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months, consistent with the package's long release gap and indicating no current maintenance capacity.

Repo issue activity

There were 26 open issues and 6 open pull requests, with no new or closed issues and no merged pull requests in the last month. This suggests unresolved work is not being actively handled.

Repo tooling

The repository uses Composer, but no security-scanning tools were detected. The missing scanning is a modest transparency gap, not evidence of an unsafe package by itself.

Security policy

The linked repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a secondary concern compared with the much older maintenance record.