ahmard/flutterwave
The project has one registry maintainer, no security policy, and no security scanning, limiting evidence of ongoing support. A README, tests, MIT license, and release notes provide useful transparency, but they do not offset the age of the codebase.
47%
Total Score
25
100
69
75
Health Score Breakdown
The latest release was over three years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a payment API client.
The repository recorded zero commits and zero active maintainers in the last three months, confirming that maintenance has stalled rather than merely having a slow release cadence.
Only one account has registry publish access. This is a thin maintainer base for a package that appears to be backed by an individual rather than an organization.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these figures provide no supporting evidence of community adoption or review.
Composer build tooling is present, but no security scanning tools were detected. For a package handling payment integrations, that leaves a meaningful maintenance and review gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ahmard |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ahmard/guzwrap Version ^2.4 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 5 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.