A security policy is absent, and both workflow actions are unpinned. The MIT license, matching repository, changelog, and organization backing provide useful transparency.
60%
Total Score
67
88
75
The package has 9 releases over about 4 years, but none in the last 12 months; the latest release was published in September 2024. This indicates a meaningful maintenance slowdown.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the absence of recent registry releases and raising abandonment concerns.
There were no new or closed issues or pull requests in the last month, with 1 issue still open. This shows little recent project interaction, though the small backlog is not severe by itself.
The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities in a payment integration.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but both of its 2 action references are unpinned. That is a workflow reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^4.0.0|^5.0 | — | — |
craftcms/commerce Version ^4.0.0|^5.0.0-beta.1 | — | — |
paynl/omnipay-paynl Version ^5.0.0 | — | — |
craftcms/commerce-omnipay Version ^4.1.0 | — | — |
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.