The focused package has clear documentation, a tiny dependency surface, and a clean release artifact. Its maintenance has effectively stopped since June 2022, and the repository lacks a security policy, so future compatibility and response capacity are uncertain.
58%
Total Score
50
100
88
75
The registry namespace and repository are owned by the same individual, providing consistent ownership context. It does not show organizational backing or a broader maintenance team.
The package has only two releases across more than eight years and none in the last four years, indicating a very slow release cadence. The stable version and focused scope partly reduce the impact, but this is still a maintenance concern.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having received no recent push since June 2022. This materially raises abandonment and compatibility risk.
Composer is used for builds, but no security scanning tooling is configured. The missing scanning is a modest transparency gap rather than evidence of an unsafe release.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This weakens maintenance transparency for a library that handles reCAPTCHA integration.
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.