Recent repository work and organization backing provide some continuity. Maintenance is concentrated in one contributor, and workflow credentials and action pinning need tighter controls.
44%
Total Score
83
100
71
75
Packagist marks the entire package as abandoned, which is a major adoption risk even though the listed replacement is the same package. This outweighs the otherwise active repository evidence.
The package has only 6 releases and no releases in the last 12 months, indicating a slow release cadence. Recent repository activity partly offsets the risk of complete abandonment.
All 3 recent commits came from one contributor, leaving maintenance dependent on a single active person. Organization backing provides some handoff capacity but does not remove the concentration risk.
The repository name does not match the package name and its README does not mention the package, creating some uncertainty about the package-to-repository relationship. The matching CoreShop organization reduces, but does not eliminate, that concern.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a hygiene and maintenance concern rather than a standalone adoption blocker.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
coreshop/core-shop Version ^3.0 || ^4.0 | — | — |
flux-se/payum-stripe Version ^2.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.