backup-manager/laravel

Documentation and packaging are clear, and the repository still matches the package with organizational ownership. However, the release line has been inactive for over six years and the repository has had no commits for over five years, increasing compatibility and abandonment risk.

Latest 2.0

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over six years ago, with no releases in the last 12 months. The long release gap materially increases abandonment and compatibility risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a repository that has been inactive for over five years. This is the strongest abandonment signal.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 22 issues remain open. This suggests limited current maintenance capacity.

Repo tooling

Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a hygiene concern rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, which reduces transparency for reporting vulnerabilities in a package that handles database backups.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Shawn McCool

Direct Dependencies

Dependency	Last Release	Score
symfony/process Version ^3\|\|^4\|\|^5	—	—
illuminate/console Version ^5.5\|\|^6\|\|^7	—	—
illuminate/support Version ^5.5\|\|^6\|\|^7	—	—
illuminate/container Version ^5.5\|\|^6\|\|^7	—	—
backup-manager/backup-manager Version ^1.0	—	—