Organization backing, a clear MIT license, and a substantial README support adoption. Maintenance is concentrated in one contributor, and the only workflow action is unpinned.
82%
Total Score
83
93
67
All two recent commits came from one contributor, leaving maintenance dependent on a single active individual. Organization backing provides some capacity for handoff but does not remove the concentration concern.
The project uses Composer build tooling, but no security-scanning tool was detected. This is a modest transparency gap rather than evidence of unsafe behavior.
The repository has no security policy, reducing guidance for reporting and handling vulnerabilities in a package that processes visitor IP data.
The single workflow was fully analyzed and uses read-only permissions with no detected injection or secret findings. Its one action reference is unpinned, which is a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^2 || ^3 | — | — |
twig/twig Version ^3.21 | — | — |
doctrine/dbal Version ^4.3 | — | — |
geoip2/geoip2 Version ^3.4 | — | — |
symfony/config Version ^7.4 || ^8.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.