The package is small, documented, tested, and has a clear MIT license with no install-time scripts. Its release and commit activity has stopped, and the repository has no security scanning or policy, so future compatibility and maintenance are uncertain.
58%
Total Score
67
100
89
83
The registry namespace and repository owner are the same individual account, rather than an organization-backed project. That leaves a relatively narrow apparent ownership base, consistent with the limited activity evidence.
The package has made seven releases since February 2018, but none in the last 12 months; the latest release was in January 2021. This indicates a long maintenance gap, although the release history shows it was previously maintained.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this is evidence of inactive maintenance and raises abandonment risk.
Composer is used as the build tool, but no security scanning tools are present. For a small package this is a hygiene gap rather than a standalone adoption blocker.
The repository has no security policy. This weakens the project's response transparency if a vulnerability is found, though it is not severe enough to make the release unfit by 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.