frankmullenger/payment-paymentexpress
The README, tests, and release notes make the integration understandable, but the project shows no recent maintenance and has unresolved repository activity. Its stable version and lack of deprecation help, yet this is a poor choice for a new dependency.
38%
Total Score
33
81
75
Health Score Breakdown
The latest release was in October 2017, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk for a payment integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No newer activity compensates for this maintenance gap.
The package has one registry publisher, Frank Mullenger. The linked repository is user-owned rather than organization-backed, so there is little visible maintainer redundancy.
Five issues and six pull requests remain open, while none were opened or closed and no pull requests were merged in the last month. This suggests unresolved maintenance work.
Composer is used for builds, which is appropriate, but no security-scanning tooling was detected. This is a modest supply-chain hygiene gap rather than a direct failure.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Frank Mullenger |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 silverstripe/cms Version 3.* | — | — |
silverstripe/payment Version 1.0.* | — | — |
silverstripe/framework Version 3.* | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 13 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.