The clear README, MIT declaration, and matching repository make adoption easier. Future fixes and security response are uncertain because the project appears inactive and has only one registry maintainer.
44%
Total Score
38
50
75
75
The package has made four releases, but none in the last 12 months; the latest release was over two years ago. This strongly suggests maintenance has stopped.
There were zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating a high risk of abandonment.
The package declares nine runtime dependencies and no development dependencies. This is a meaningful dependency surface for a Laravel package, though the signal alone does not show that the dependencies are unsafe or unmaintained.
Only one account has registry publishing access. Because the project is user-owned rather than organization-backed, this leaves a thin publishing and maintenance base.
The registry namespace and repository owner match, but both identify a single user account rather than an organization, offering limited visible continuity if that maintainer stops work.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
artesaos/seotools Version ^v0.22.1 | — | — |
laravel/framework Version ^6|^7|^8 | — | — |
devcuongnguyen/crud Version ^1.0.0 | — | — |
spatie/laravel-sitemap Version ^5.8 | — | — |
devcuongnguyen/settings Version ^1.0.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.