fomvasss/laravel-backup-ui
The package has strong practical documentation, tests, a changelog, and an MIT license. Its small audience, single-contributor maintenance, absent security policy, and entirely unpinned workflow actions leave meaningful long-term and build-integrity concerns.
70%
Total Score
63
100
89
67
Health Score Breakdown
Only one registry account has publish access. The repository is also user-owned rather than organization-owned, so there is no visible organizational handoff capacity to offset this concentration.
The repository is owned by the same individual namespace as the package and is user-owned, confirming that the single-maintainer risk is not visibly backed by an organization.
One contributor made all 5 commits in the last 3 months, giving the project a bus factor of one and increasing abandonment and handoff risk.
The repository has 2 stars, no forks, and no watchers. Popularity is not required for a healthy package, but these counts provide little evidence of a broad support community.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 fomvasss |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/framework Version ^10.10|^11|^12|^13 | — | — |
spatie/laravel-backup Version ^9.0|^10 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 8 months 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.