payioltd/payio
The small dependency surface and matching organization repository make the package relatively easy to inspect. Maintenance stopped nearly five years ago, with no recent commits or releases, and the repository has no security policy or tests. Pinning this version should be treated as a long-term maintenance liability.
45%
Total Score
50
100
79
83
Health Score Breakdown
The latest release was about 4 years and 7 months ago, with no releases in the last 12 months. That is a substantial abandonment concern for a payment integration.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and indicating no visible ongoing maintenance.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest hygiene gap rather than evidence of an unsafe release.
The linked repository has no security policy. That weakens the project's vulnerability-reporting and response transparency, which matters for payment software.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jamie Laughton |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 4 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.