yasinkuyu/omnipay-posnet
The package has a clear README, tests, MIT licensing, and a small dependency footprint. There is no security policy, and the limited repository activity reduces confidence in ongoing maintenance.
58%
Total Score
25
100
79
75
Health Score Breakdown
The package has only two releases, with the latest on September 15, 2017 and none in the last 12 months. This is strong evidence of dormant maintenance for a payment gateway.
There were zero commits and zero active maintainers in the last three months, reinforcing the long gap since the last release and leaving little evidence of current maintenance.
There were no new or closed issues or pull requests in the last month, with two open issues remaining. This provides no recent evidence of issue handling.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap, not evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This matters for a package that handles payment gateway integrations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Yasin Kuyu |
| Omnipay Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 11 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.