It has a clear MIT license, tests, a matching repository, and a minimal dependency footprint. The repository lacks a security policy, and its workflow uses two unpinned actions.
62%
Total Score
50
100
88
50
The package has had no release in more than two years, after ten releases overall. That long gap lowers confidence in ongoing maintenance, though the release history shows an initially active project.
There were no commits and no active maintainers in the last three months, consistent with the package having gone more than two years without a release. This is a concrete abandonment concern for a library dependency.
Composer build tooling is present, but no security scanning tool is configured. That is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This matters for a library intended to be integrated into other applications.
The workflow was fully analyzed, uses read-only permissions, and has no dangerous triggers or audit findings. However, both of its action references are unpinned, which leaves the build exposed to changes in those referenced actions.
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.