The package includes a substantial README, tests, a stable release, and a clear MIT declaration. Its one-person maintenance base, absent security policy, and lack of repository activity since August 2024 increase the risk of unsupported fixes.
55%
Total Score
50
100
88
75
Only one account has registry publishing access. That is a thin publishing base for an independently owned project and increases continuity risk when repository activity is already absent.
Only two releases exist, with no release in the last 12 months; the latest release was published on August 28, 2024. This indicates slow or stopped maintenance for a package handling database backups.
There were zero commits and zero active maintainers in the last three months. Together with the old latest release, this is concrete evidence that maintenance has stopped or substantially slowed.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance weakness, not evidence that the package is unsafe.
The repository has no security policy. For a database backup and restore library, this leaves no documented channel or process for reporting security issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/process Version ^4.2|^5.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.