innoweb/silverstripe-silvershop-stripe
The BSD-3-Clause license, clear README, changelog, and focused dependency set make integration straightforward. Security coverage is limited, with no repository security policy or security scanning, so ongoing maintenance deserves attention.
67%
Total Score
63
100
89
83
Health Score Breakdown
The source repository is owned by an individual user rather than an organization, so the single-contributor maintenance pattern is not visibly backed by a broader team.
All one recent commit came from a single contributor, leaving maintenance dependent on one person; the repository owner is an individual rather than an organization, so there is no shown organizational handoff capacity.
One commit was recorded in the last three months, showing some recent activity but a low maintenance rate for a package handling payment integration.
Composer build tooling is present, but no security scanning tools were detected, leaving security checks less visible than they could be.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Florian Thoma |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/stripe Version ^3.0 | — | — |
silvershop/core Version ^3.1 | — | — |
silverstripe/cms Version ^5 | — | — |
silverstripe/vendor-plugin Version ^2 | — | — |
Weekly Downloads
Info
- Last Published
- 11 months ago
- Created
- 7 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.