The project has tests, a clear MIT license, and no install-time scripts. Its small footprint and unpinned workflow actions leave limited maintenance and build-transparency evidence.
61%
Total Score
75
100
81
75
The latest release was over two years ago, with no releases in the last 12 months, despite a previously regular release interval of about 59 days. This is a meaningful maintenance concern.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
The repository name does not match the package name and its README does not mention this package, so the repository-to-package relationship is not clearly established. Organization backing partly reduces concern but does not remove the transparency gap.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency gap for ongoing dependency maintenance.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
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.