The package has a clear README, tests, release notes, and matching MIT license. Its minimal runtime footprint and read-only workflow permissions are reassuring, but security tooling is absent.
67%
Total Score
50
100
83
50
The package has existed since 2015, but only four releases are recorded and none occurred in the last 12 months; the latest release was about 19 months ago. This suggests limited ongoing maintenance, despite its long history.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. This is meaningful abandonment risk for a library dependency.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest maintenance and assurance gap rather than a severe dependency risk.
The repository has no security policy, which reduces disclosure transparency for a package that processes client IP information. The small scope and otherwise clear project structure partly limit the concern.
The single workflow was fully analyzed, uses read-only permissions, and has no reported dangerous findings, but both of its two action references are unpinned. That leaves avoidable build-integrity exposure.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.