verbb/commerce-payflow
Healthy and suitable to use, with a small maintenance team as the main caveat. It has a current stable release, established history, organizational backing, licensing, and a linked active repository, but recent work is concentrated in one contributor and the project has no automated security scanning.
78%
Total Score
80
100
83
100
Health Score Breakdown
The package includes a README and changelog, and the repository uses GitHub Releases; missing tests are a modest transparency gap because no repository tests are present either.
All recent commits came from one contributor, creating concentration risk; organizational backing partly compensates because maintenance can be handed off within the organization.
One commit was recorded in the last 3 months, showing some recent activity but a very limited maintenance cadence.
The repository has only 3 stars and 4 forks, which provides little community validation, but low popularity alone does not outweigh the package's other evidence.
Composer is used for builds, but no security scanning tools are configured, leaving a security-hygiene gap for a payment-related package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Verbb |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 verbb/base Version ^3.0.0 | — | — |
craftcms/cms Version ^5.0.0 | — | — |
omnipay/payflow Version ^3.0.0 | — | — |
craftcms/commerce Version ^5.0.0 | — | — |
craftcms/commerce-omnipay Version ^4.1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 days 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.