yomafleet/payment-provider
A small dependency set, MIT licensing, and a tested source tree make the package easy to inspect and integrate. The organization-backed project lacks a security policy and automated security scanning, limiting transparency around future maintenance.
62%
Total Score
75
100
83
75
Health Score Breakdown
The package has only 3 releases and none in the last 12 months; its latest release was over 2 years ago. This indicates a meaningful maintenance gap, despite the stable release history.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release gap and increasing abandonment risk.
The repository has 4 stars, 1 fork, and 0 watchers. This is limited adoption evidence, but popularity is only supporting evidence and does not outweigh the maintenance signals.
Composer is used as the build tool, but no security-scanning tools are configured. That leaves a meaningful transparency gap for a payment-related integration.
The repository has no security policy. For a payment package, the absence of a documented reporting process weakens maintenance and vulnerability-response transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Phyo Wai Linn |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^6.3.1|^7.0.1 | — | — |
simplesoftwareio/simple-qrcode Version ~4 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 4 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.