The MIT declaration and release notes provide basic transparency. There is no security policy or scanning, and the project shows no recent issue, pull-request, or commit activity.
38%
Total Score
50
33
50
The package has had no release in more than six years, with only four releases overall and none in the last 12 months. This strongly raises abandonment risk despite the short early release interval.
The release and repository each contain only four files, including a single source file and a very short README. A small package can be legitimate, but this provides little evidence of maturity or maintenance depth.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but it shows no current maintenance activity.
The linked repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less transparent and warrants caution.
Composer build tooling is present, which supports reproducible package setup, but no security scanning tools were detected. The missing scanning is a modest hygiene concern rather than proof of an unsafe release.
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.