Clear documentation, licensing, and a minimal Composer setup reduce adoption friction. The small codebase has no tests or security scanning, so maintenance changes may be harder to validate.
58%
Total Score
50
88
75
The registry lists one maintainer, which creates a thin continuity base for a package whose repository is also maintained by an individual.
The package and repository are owned by the same individual rather than an organization, so the single-person maintenance model is not supplemented by visible organizational backing.
The package had 7 releases, but none in the last 12 months and the latest release was about 21 months ago. This indicates a meaningful maintenance gap for an API client.
There were no commits and no active maintainers in the last 3 months, consistent with activity having stopped around 20 months ago.
Composer build tooling is present, but no security scanning tools are configured. That leaves an avoidable validation gap in a dependency handling an external signing API.
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.