The package has a clear MIT license, tests, a readable README, and a GitHub release for this version. Its small release history and no commits in the last three months limit confidence in ongoing maintenance, while the repository has no security policy or scanning tools.
68%
Total Score
50
100
88
83
The repository owner is an individual account rather than an organization. That provides less visible institutional backing, while the matching repository and package references provide some compensating ownership evidence.
Only two releases exist across about 15 months, with one release in the last 12 months and a typical interval of about 11 months. This is a thin maintenance record for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months. That is direct evidence of currently inactive development and raises abandonment risk.
The project uses Composer, but no security scanning tools were detected. The missing scanning coverage is a modest supply-chain hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. This weakens the project's documented process for receiving and handling vulnerabilities, although it does not by itself show an active security issue.
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.