The MIT license, release notes, README, and Composer build support basic transparency and use. However, only one release exists, nearly five years old, with no recent commits, while the repository does not clearly identify this package.
45%
Total Score
0
69
100
The package has only one release, published nearly five years ago, with no releases in the last 12 months. This is strong evidence of an immature or abandoned release line.
The repository recorded no commits and no active maintainers in the last three months, consistent with the last push being nearly four years ago. This materially raises abandonment risk.
The linked repository name does not match the package name and its README does not mention the package, so the source association is less transparent than expected.
Composer is used as a build tool, providing basic project tooling, but no security scanning tools are configured. The missing scanning is a modest transparency gap rather than evidence of unsafe behavior.
The latest version is v0.1 and is not a stable major release, indicating an early-stage API. This compounds the limited release history but is not a deprecation signal.
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.