The small, focused artifact has tests, documentation, an MIT license, and no runtime dependencies. Its solo ownership and absent security tooling leave little visible maintenance capacity.
58%
Total Score
50
100
86
75
The registry lists one maintainer, and the repository owner is an individual rather than an organization. This leaves a thin visible maintainer base if that person becomes unavailable.
The package has only one release, published about 3 years and 6 months ago, with no releases in the last 12 months. That materially raises abandonment risk.
There were no commits and no active maintainers in the last 3 months. Combined with the single old release, this points to limited current maintenance.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. For a small library this is a transparency gap, though it is less serious than evidence of unsafe release behavior.
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.