The package includes tests, a substantial README, a GitHub release, and a clear MIT license. Its single maintainer, absent recent commits, and repository naming mismatch make long-term support and package ownership less certain.
46%
Total Score
25
75
75
Only two releases exist, both published in July 2024, with no releases in the last 12 months. This is meaningful evidence of a largely inactive release process.
The repository had zero commits and zero active maintainers in the last three months, consistent with the package's old release history and raising abandonment risk.
The registry lists one publishing maintainer. That is a thin publishing base for a substantial Laravel application and provides little redundancy if that account becomes inactive.
The linked repository name does not match the package name and its README does not mention the package, so ownership of the published package is less transparent.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/dbal Version ^2.10 | — | — |
mews/purifier Version ^2.0|^3.2 | — | — |
jenssegers/date Version ^4.0 | — | — |
laravel/framework Version ^5.1|^6.0|^7.0|^8.0|^9.0|^10.0|^11.0 | — | — |
illuminate/support Version ^5.1|^6.0|^7.0|^8.0|^9.0|^10.0|^11.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.