The project is newly published, with no commit activity or active maintainers recorded in the last three months. Clear documentation, tests, licensing, organization backing, and read-only workflow permissions provide useful support, but unpinned actions and no security policy leave avoidable maintenance gaps.
58%
Total Score
75
100
79
67
All three releases were published on the same day, so there is not yet enough history to demonstrate sustained maintenance. This is an early maturity concern rather than evidence of abandonment by itself.
The repository recorded zero commits and zero active maintainers in the last three months. Because the package is only newly published, this is a meaningful but not conclusive maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for an SDK handling API credentials.
The repository has no security policy. This makes vulnerability reporting and coordinated fixes less clear, though it is not a severe risk on its own.
Version v0.1.2 is a stable, non-prerelease release, but the package has not reached a stable major version and has no longer-term release record to support confidence.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.