cmsgears/module-stripe
The organization-owned repository is not archived, and the package has a clear license and README. It lacks security tooling and a security policy, adding uncertainty for a payment integration.
38%
Total Score
50
71
50
Health Score Breakdown
The latest release was in November 2021, with no releases in the last 12 months and only six releases across more than nine years. This strongly indicates abandonment risk.
The repository had zero commits and zero active maintainers in the last three months, consistent with no release activity since November 2021. This is a substantial maintenance risk.
Composer build tooling is present, but no security scanning tooling is configured. That is a meaningful hygiene gap for code handling payment flows.
The repository has no security policy, leaving no documented reporting or response process for vulnerabilities in a payment-related module.
The assessed release is still a prerelease after the package's long history, and all recent releases are prereleases. That signals limited maturity for 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 |
|---|---|---|
 stripe/stripe-php Version 6.4.* | — | — |
cmsgears/module-cart Version * | — | — |
cmsgears/module-core Version * | — | — |
cmsgears/module-payment Version * | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 9 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.