omarusman/omnipay-paymongo
There is no security policy or automated security scanning, which limits transparency for a payment integration. The package has a README, tests, matching source repository, and an MIT license, but ongoing support appears limited.
52%
Total Score
25
100
83
75
Health Score Breakdown
The package has had only two releases, both in March 2020, with no release in more than six years. That is a substantial maintenance concern for a payment integration.
There were no commits and no active maintainers in the last three months, consistent with a project that is not currently being maintained.
There were no new or closed issues or pull requests in the last month, while one issue and two pull requests remain open. This suggests limited recent responsiveness.
Composer build tooling is present, but no security-scanning tools were detected. For payment-processing code, that is a meaningful transparency and maintenance gap.
The repository has no security policy, leaving no documented path for reporting vulnerabilities or handling security fixes.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Omar Usman |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 kitetail/zttp Version ^0.6.0 | — | — |
omnipay/common Version ^3.0 | — | — |
php-http/guzzle6-adapter Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 6 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.