novalnet/sprykerb2c-payment
The package has clear integration documentation, a changelog, and organization backing. Its release history is stale, with no releases in nearly four years and no recent commits, while repository security safeguards are limited.
58%
Total Score
50
70
50
Health Score Breakdown
Only three releases have been published, with no release in nearly four years and none in the last 12 months. That materially increases compatibility and abandonment risk for a payment integration.
There were no commits and no active maintainers in the three months measured. This indicates current maintenance has stopped or become very limited, despite the repository's later push date.
Composer is used for the build, but no security scanning tools were detected. For a payment module, that is a meaningful repository hygiene gap.
The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities in a payment integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/oms Version ^7.0.0 || ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/quote Version ^2.0.0 | — | — |
spryker/sales Version ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/refund Version ^5.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 5 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.