The small project has no recent commit activity and no security policy, which leaves limited evidence of ongoing maintenance for encryption code. Its clear MIT licensing, matching repository, simple dependency profile, and recent stable release history are reassuring.
62%
Total Score
50
100
88
75
Only one registry maintainer account is listed, creating a thin publishing base. The linked repository is also user-owned rather than organization-owned, so there is no provided backing signal to offset that concentration.
The package has 3 releases since June 2025, with 1 release in the last 12 months and a median interval of about 82 days. This shows some release history but limited evidence of sustained activity.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, indicating that maintenance has currently gone quiet. This is a meaningful abandonment concern, though the latest release was published recently enough to provide some counterweight.
Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a modest hygiene gap rather than a severe dependency-health problem by itself.
The repository has no security policy, leaving no documented route for reporting vulnerabilities in a package implementing payment-gateway encryption. The package's narrow scope does not remove the value of this transparency.
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.