It has a stable major release, tests, a license, and a repository that clearly matches the package. The project has had no release or commit activity for more than five years, and its repository lacks security scanning and a security policy.
58%
Total Score
50
100
88
80
The package and repository are owned by the same individual account rather than an organization, so there is no organizational backing to offset the project's thin maintenance capacity.
The package has seven releases since 2018, but its latest release was over five years ago and it has had no releases in the last 12 months. That materially increases abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the long release gap and indicating very limited current maintenance.
The repository uses Make and Composer, providing basic build tooling, but it has no security scanning tools. This is a modest transparency and maintenance gap.
The repository has no security policy. For a small library this is not severe on its own, but it reduces the clarity of vulnerability reporting and maintenance expectations.
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.