spryker/payment-app-extension
The repository lacks a published security policy and only half of its workflow actions are pinned. Release activity is sparse, but recent commits, five active contributors, organization ownership, release notes, and a documented package keep maintenance risk moderate.
80%
Total Score
100
100
86
67
Health Score Breakdown
Only two releases have been published, with none in the last 12 months, which suggests a slow release cadence. Recent repository activity partly compensates for this maintenance concern.
Composer build tooling is present, but no security scanning tool was detected. This is a modest hygiene gap, not evidence of unsafe behavior on its own.
The repository has no published security policy, leaving vulnerability reporting and response expectations less transparent.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, a modest reproducibility gap rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/transfer Version ^3.27.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.