The project has tests, release notes, a matching repository, and organization backing. Its maintenance record is thin, with no commits or releases in about one year, while workflow references are all unpinned and no security policy or scanning is present.
58%
Total Score
75
100
78
67
Only two releases exist, both published about one year ago, with no releases in the last 12 months. That leaves limited evidence of sustained maintenance.
There were no commits and no active maintainers in the last three months, consistent with roughly a year since the last push. This is the clearest abandonment concern in the available evidence.
The repository has 4 stars and 1 fork, indicating limited adoption. Popularity is supporting evidence, so this modestly lowers confidence in project maturity but is not decisive alone.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-maintenance gap.
The repository has no security policy, so vulnerability reporting and response expectations are not documented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/laravel-data Version ^4.17 | — | — |
spatie/laravel-responsecache Version ^7.7 | — | — |
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.