The MIT license, matching repository, and organization backing make its provenance clear. Documentation is minimal, and the project has no security policy or scanning evidence.
38%
Total Score
50
64
50
This is the package's only release, published about six years ago, with no releases in the last 12 months. That strongly indicates abandonment risk.
The repository has had no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no observed maintenance activity.
The package includes a README, but it is only five characters long and provides effectively no consumer guidance. The absence of tests and a changelog is normal for a published artifact and is not counted against it.
Composer is used for the build, which is appropriate, but no security scanning tools are present. This is a modest supply-chain hygiene gap in an otherwise identified build setup.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though not evidence of a vulnerability itself.
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.