The package includes tests, release notes, a clear license, and no runtime dependencies. Its repository is very small, lacks a security policy, and does not clearly identify the package in its README, so maintenance and ownership deserve extra scrutiny.
58%
Total Score
50
100
71
83
The package has had only three releases, with none in the last 12 months; its latest release was over two years ago. This is meaningful evidence of slowing maintenance for a still-developing 0.x package.
The repository recorded no commits and had no active maintainers in the last three months, consistent with the latest push being over two years ago. This materially raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository is specifically the package's source rather than a loosely related project.
Composer is used for the build, but no security-scanning tooling is present. The missing scanner is a hygiene gap rather than evidence that the package is unsafe by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. For a small package this is a modest transparency concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.