The small dependency set, clear README, MIT license, and organization ownership provide useful support. Long-term maintenance is still uncertain because the project is only 69 days old and all recent commits come from one contributor.
61%
Total Score
67
100
79
88
The package is only 69 days old with three releases, including three in the last 12 months, so its maintenance record is still limited. The roughly five-day median release interval shows active early development rather than abandonment.
All three recent commits came from one contributor, creating a narrow maintenance base. Organization ownership provides some ability to hand off maintenance, but no second active contributor is shown.
The repository recorded three commits in the last three months, showing some recent work. However, the activity level is still small for judging sustained maintenance.
Composer is used for the build, but no security scanning tools are reported. For a client handling server-side keys and fraud decisions, that is a meaningful repository hygiene gap.
The repository has no security policy. That weakens the documented process for reporting and handling vulnerabilities in a security-sensitive server client.
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.