apiato/payment-container
The README is brief and the package has two runtime dependencies. MIT licensing and organization ownership provide some transparency, but the source offers little evidence of ongoing care.
42%
Total Score
50
64
75
Health Score Breakdown
The package has made no release in about five years and five months, despite 16 releases concentrated near its launch. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No newer activity compensates for that inactivity.
A README and GitHub release are present, but the README explicitly says the container is not fully tested; that is a meaningful concern for payment integration. The absence of tests in the published artifact is not itself a gap.
One issue remains open and there has been no issue or pull-request activity in the last month. This supports the broader picture of limited current maintenance, though the issue count is small.
The repository has one star, one fork, and one watcher, providing little independent evidence of adoption or community support. Low popularity is supporting evidence only and does not determine health.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 mohammad-alavi/laravel-shoppingcart Version ^0.1.2 | — | — |
apiato/stripe-payment-gateway-container Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 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.