craftcms/commerce-omnipay
The release line is established and still receiving updates, with a maintained source tree and clear project ownership. Maintenance is concentrated in one recent contributor, and the repository lacks security scanning while its workflow actions are all unpinned.
78%
Total Score
80
100
94
100
Health Score Breakdown
All three recent commits came from one contributor, creating concentrated maintenance risk; organization backing provides some handoff capacity but no second active contributor is shown.
The repository has four open issues and one open pull request, but no issues or pull requests were opened or merged in the last month, indicating limited recent community activity.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance-hygiene gap.
All three workflows were analyzed with no audit findings or untrusted execution sinks, but all three action references are unpinned, which weakens build reproducibility and action supply-chain hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Pixel & Tonic |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ^3.0 | — | — |
craftcms/commerce Version ^4.0.0|^5.0.0-beta.1 | — | — |
php-http/guzzle7-adapter Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months 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.