yk/laravel-backup

Documentation is present, licensing is clear, and installation has no lifecycle scripts. The tiny codebase has no tests or security policy, so future Laravel compatibility and backup behavior are hard to validate.

Latest 1.0

Packagist

39%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published in January 2017, with no releases in the following nine years. That is strong evidence of abandonment for a framework-integrated backup library.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving no observed maintenance capacity.

Package scaffolding

A readable README, a GitHub release for version 1.0, and clear licensing provide useful consumer documentation, but the package and repository contain no tests. The absent tests are a meaningful validation gap for commands that can erase and restore database tables.

Repo popularity

The repository has one star, zero forks, and one watcher, providing little evidence of community review or shared maintenance. Popularity is supporting evidence rather than decisive on its own, but it does not offset the inactive history.

Repo tooling

Composer is used for the build, but no security-scanning tools are configured. That is a hygiene gap, not evidence of malicious behavior, and it offers no compensating assurance for an old inactive release.