Laravel package to detect malicious IPs, ban them via Cloudflare, and report to AbuseIPDB
68%
Total Score
70
100
88
75
Only one registry account has publish access. That is not evidence of poor work by itself, but it leaves little publishing redundancy for this independently owned project.
The repository is owned by an individual account rather than an organization, so the concentrated contributor and single registry maintainer provide little visible organizational backup.
The package is young at 96 days old but has four releases, all within the last 12 months, with a median interval of about 15 days; this indicates active early maintenance, though long-term history is limited.
One contributor made all four commits in the last three months, so maintenance depends entirely on a single active individual with no observed handoff capacity.
Composer build tooling is present, but no security-scanning tool was detected. For a package that handles Cloudflare and AbuseIPDB integrations, this is a review gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.54|^12.0|^13.0 | — | — |
illuminate/queue Version ^11.54|^12.0|^13.0 | — | — |
illuminate/events Version ^11.54|^12.0|^13.0 | — | — |
illuminate/console Version ^11.54|^12.0|^13.0 | — | — |
illuminate/support Version ^11.54|^12.0|^13.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.