coreshop/payum-saferpay-bundle
Clear licensing, focused dependencies, and release notes make the package understandable to adopt. Maintenance is concentrated in one contributor, while workflow credentials and unpinned actions leave avoidable operational risk.
66%
Total Score
67
100
88
67
Health Score Breakdown
The package has 11 releases but none in the last 12 months, with the latest registry release nearly three years ago. Recent repository activity partly offsets the stale registry cadence, but the release gap remains a maintenance concern.
One contributor made all three recent commits, creating a narrow operational bus factor. Organization ownership provides some handoff capacity, but no second recently active contributor is shown.
The repository recorded three commits in the last three months, indicating current activity. All activity came from one maintainer, so continuity remains limited.
The project uses Composer, but no security-scanning tool was detected. That is a modest transparency and maintenance gap rather than evidence of unsafe code.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear for a payment integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 DACHCOM.DIGITAL Stefan Hagspiel |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 coreshop/core-shop Version ^2.2|^3.0|^4.0 | — | — |
karser/payum-saferpay Version ^0.3 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.