The clear README, MIT license, and exact-version release notes improve transparency, while the small implementation keeps the dependency surface limited. Its only release was about six years ago, with no recent commits, tests, or security policy, so maintenance risk is substantial.
42%
Total Score
0
100
60
50
This is the package's only release, published about six years ago, with no releases in the last 12 months. That strongly limits evidence of ongoing maintenance.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and indicating likely abandonment risk.
The repository name matches the package, but its README does not mention the package name. This creates a modest ownership and packaging-transparency concern, though the matching repository name is compensating evidence.
Composer is used for the build, but no security-scanning tools were detected. This is a hygiene gap rather than a severe risk, especially for the package's small dependency surface.
The linked repository has no security policy, reducing transparency about how vulnerabilities would be reported or handled. This matters more alongside the absence of recent maintenance evidence.
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.