andrewnovikof/omnipay-sberbank
The package includes a clear README, broad tests, and matching MIT licensing. Its single-user ownership and lack of repository security scanning reduce confidence for a payment integration.
57%
Total Score
50
88
50
Health Score Breakdown
Only one registry publishing account is listed. That is not inherently unhealthy for a user-owned project, but it leaves a thin visible publishing base alongside the inactive repository.
The package has had no release in nearly 3 years, despite a long history and 10 total releases; this is a meaningful maintenance concern.
There were no commits and no active maintainers in the last 3 months, consistent with a project whose maintenance has stopped since October 2023.
There was no issue or pull-request activity in the last month, with four open issues and one open pull request; this adds to the signs of limited ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected, leaving a transparency and maintenance-control gap for a payment integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 AndrewNovikof |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ^3.2 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 8 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.