taki47/otpsimplepay
The MIT license and clear README support adoption, while the one-person project has no security policy or scanning. The payment integration lacks recent maintenance evidence, so its long-term reliability is uncertain.
38%
Total Score
25
78
75
Health Score Breakdown
The latest release was about 5 years ago, with no releases in the last 12 months. Although the package had five releases during its initial development, the prolonged release gap indicates abandonment risk.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long gap since the last release and showing no current maintenance capacity.
A single registry maintainer is a thin base for a payment integration, increasing bus-factor and continuity risk. The repository is user-owned rather than organization-backed, so there is no provided backing signal to compensate.
The repository has 0 stars, 1 fork, and 1 watcher. Low adoption is only supporting evidence, but it provides little community validation or backup for the inactive project.
Composer build tooling is present, but no security scanning tools were detected. That is a meaningful hygiene gap for a package handling payment integration code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 taki47 |
Direct Dependencies
No direct dependencies.
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.