btrl/ipay-card-on-file
Clear licensing, a focused dependency set, and organization-backed ownership support adoption. The small release history and absent recent commits leave maintenance continuity uncertain, while missing security scanning and a security policy add modest transparency concerns.
64%
Total Score
75
86
75
Health Score Breakdown
Only two releases have appeared over about 23 months, with roughly 363 days between them and one release in the last 12 months. This is a thin maintenance record, though the latest release includes concrete compatibility notes.
The repository recorded zero commits and zero active maintainers in the last 3 months, following the October 2025 release. That leaves current maintenance capacity unproven rather than demonstrating abandonment on its own.
The project uses Composer, which fits the package, but no security-scanning tool was detected. This is a modest process gap for a payment-related integration.
The linked repository has no security policy. For a payment module, that reduces transparency around how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 btrl/ipay Version ^100.0 | — | — |
magento/module-payment Version ^100.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 months ago
- Created
- 1 year 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.