beechit/backup-restore
The small dependency set, clear README, and matching organization repository improve transparency. However, there have been no releases or commits for more than five years, and the repository has no security policy or scanning.
38%
Total Score
50
100
75
75
Health Score Breakdown
The package has had no release in more than five years, despite eight releases overall; this is strong evidence of abandonment risk for a backup tool.
There were zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped for years.
The repository has one open issue and no issue or pull-request activity in the last month, providing no evidence of active support.
Composer build tooling is present, but no security scanning tools are configured; this is a meaningful transparency and maintenance gap for a package handling backups.
The repository is not archived, which preserves a path for maintenance, but its last push was in February 2021 and does not show current activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 typo3/cms-core Version ^10.3 | — | — |
helhum/typo3-console Version ^6.1 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.