paytic/omnipay-twispay
The MIT license, matching repository, tests, and clear README support adoption. A single registry maintainer and no security policy reduce confidence in ongoing support.
63%
Total Score
67
100
81
75
Health Score Breakdown
Only one account has registry publish access. The organization-backed repository provides some context, but the narrow publishing base still reduces operational resilience.
The package has 12 releases, but none in the last 12 months and the latest was over 2 years ago, which indicates inactive release maintenance.
There were zero commits and zero active maintainers in the last 3 months, consistent with an inactive project and increasing abandonment risk.
The repository uses Composer build tooling, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The linked repository is not archived, but its last push was over 2 years ago, so this does not offset the broader inactivity evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Gabriel Solomon |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 paytic/omnipay-common Version ^3.0 || ^4.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 9 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.