The package is clearly licensed, narrowly scoped, and includes repository tests plus release notes. Its single release and inactive repository, along with absent security scanning and unpinned workflow actions, make long-term maintenance and build trust uncertain.
41%
Total Score
25
70
50
The package has only one release, published over six years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no recent maintenance.
One registry maintainer is sufficient for a small package, but it provides little redundancy when the project also shows no recent release or commit activity.
Composer is used for the build, but no security scanning tools are configured. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy, reducing clarity about vulnerability reporting and maintenance response. The package's small scope limits the significance of this gap.
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.