maxts/omnipay-bundle
A single maintainer, no security policy, and no security scanning limit ongoing oversight. The package is well-scaffolded and licensed, but its last release and repository activity were about 10 years ago, making abandonment the main concern.
35%
Total Score
25
100
75
88
Health Score Breakdown
The package has made no releases in the last 12 months, and its latest release was about 10 years ago. This strongly indicates abandonment risk despite the package having two historical releases.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history showing no activity for about 10 years.
One registry maintainer is a thin publishing base, although the repository is user-owned rather than organization-owned, so this provides limited ongoing capacity.
The repository has 0 stars and 0 forks, with 1 watcher. Low adoption is supporting evidence of limited project traction, but it is not decisive by itself.
The project uses Composer but has no detected security scanning tools. Composer provides normal build tooling, while the missing scanning reduces supply-chain transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Colin O'Dell |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
symfony/framework-bundle Version ~2.3 | — | — |
Weekly Downloads
Info
- Last Published
- 11 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.