Usable with caveats: the package is small, clearly backed by its matching organization repository, licensed, and not deprecated. However, it has had only two releases and no commits in over two years, so ongoing maintenance appears uncertain.
58%
Total Score
75
100
81
83
Only two releases were published, with the latest release more than two years ago and no releases in the last 12 months. This is a meaningful maintenance concern for a dependency, despite the package being stable at version 1.0.1.
The repository recorded zero commits and zero active maintainers in the last three months. Given the package's age and last release date, this indicates little recent maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk for this small package.
The linked repository is not archived, but its last push was over two years ago. The non-archived status is positive, while the old last-push date is consistent with the maintenance concern from the release and commit history.
The repository has no security policy. That weakens the project's documented vulnerability-reporting process, although it does not by itself show that the package is unsafe to use.
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.