No commits in the last three months and no security policy reduce confidence in ongoing care. Documentation, tests, stable releases, and a clean workflow audit provide useful counterweight.
76%
Total Score
75
94
75
There were zero commits and zero active maintainers in the last three months. Despite a recent release and repository push, this weakens confidence in current maintenance capacity.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest security-hygiene gap rather than evidence of abandonment.
The repository has no published security policy. That reduces transparency about vulnerability reporting and response expectations.
All workflows were analyzed without audit findings or untrusted checkout and script-injection sinks. However, both action references are unpinned, which leaves the build exposed to changing action code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
torann/geoip Version ^1.0|^3.0 | — | — |
nesbot/carbon Version ^2.0|^3.0 | — | — |
illuminate/support Version ~5.5.0 || ~5.6.0 || ~5.7.0 || ~5.8.0 || ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
spatie/laravel-referer Version ^1.6 | — | — |
jaybizzle/crawler-detect Version ^1.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.