Risky to adopt for a new project: the package has had no release or repository activity for about six years and has almost no community traction. It is not deprecated or archived, and the repository matches the package with a usable README, but maintenance appears effectively stopped.
46%
Total Score
25
72
83
The package has had no releases in the last 12 months, and its latest release was published about six years ago. That long period without updates is a substantial abandonment concern for a Laravel dependency.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push being about six years ago. This is the strongest evidence that ongoing maintenance capacity is absent.
The registry namespace and repository owner are the same individual account, providing direct ownership alignment. There is no organization backing to offset the project's very small maintenance base.
The repository has zero stars, one fork, and one watcher, indicating very limited public adoption or review. Popularity is supporting evidence, but this reinforces the maintenance concern.
The repository uses Composer build tooling, but it has no security scanning tools. The missing scanning is a hygiene gap, though it is less serious than the lack of maintenance activity.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.