The codebase is very small, with only two runtime requirements and no install-time scripts. The MIT declaration and matching repository support transparency, but the project offers little evidence of active stewardship.
38%
Total Score
25
79
50
The package has made only one release, on July 22, 2022, and none in roughly four years. This strongly suggests abandonment risk despite the stable 1.0.0 version.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and indicating no current maintenance.
One registry maintainer publishes the package. That is not inherently unhealthy for a small library, but it leaves little visible maintenance capacity when activity has stopped.
Composer build tooling is present, but no security-scanning tools are configured. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a package that may handle API integrations, this weakens vulnerability-reporting transparency, though it is less serious than the maintenance 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.