The repository has seen no commits for about 11 months, and only one release in the last year, so fixes may be slow. Clear documentation, an MIT license, and a matching repository help, but the solo maintainer and absent security policy leave limited assurance.
61%
Total Score
50
100
83
83
Only one registry account has publish access. The matching user-owned repository shows direct ownership, but the narrow publishing base provides limited redundancy.
The registry namespace and repository are owned by the same individual account, providing consistent ownership context but no organizational backing.
The package has 29 releases over about four years and one release in the last 12 months, showing an established history but limited recent release activity.
There were zero commits and zero active maintainers in the last three months, with the repository last pushed about 11 months ago. That materially raises the risk that fixes and updates will be slow.
There are no open issues or pull requests and no recent issue or pull request activity. This is compatible with a small stable project, but offers little evidence of an active support channel.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^11.0|^12.0 | — | — |
spatie/laravel-package-tools Version ^1.9.2 | — | — |
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.