Clear licensing, organization backing, and release notes support straightforward adoption. The repository lacks security scanning and a security policy, while its recent development activity is quiet; monitor future releases closely.
62%
Total Score
50
100
94
83
There were no commits and no active maintainers in the last three months. That is a meaningful maintenance warning for a payment integration, despite the recent repository push and release history.
There were no new or closed issues or pull requests in the last month, with one open pull request. This supports the picture of quiet current activity but is less severe than an archived project.
Composer build tooling is present, but no security-scanning tools were detected. For payment-processing software, that is a genuine repository hygiene gap.
The repository has no security policy. This weakens vulnerability-reporting transparency for an integration that handles payment workflows.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
multisafepay/magento2-core Version ^3.17 | — | — |
multisafepay/magento2-frontend Version ^3.0 | — | — |
multisafepay/magento2-adminhtml Version ^1.37 | — | — |
hyva-themes/magento2-hyva-checkout Version ^1.1.29 | — | — |
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.