fapshi/payments
The README, MIT declaration, and small dependency set make integration straightforward. Organizational backing and a non-archived repository help, but the project has not shown ongoing maintenance since its sole release.
60%
Total Score
75
100
83
75
Health Score Breakdown
This is a young package with one release, published about 10 months ago, and no subsequent releases. That limited track record makes long-term maintenance less certain.
The repository recorded zero commits and zero active maintainers in the last three months, and its last push was around 11 months ago. That is the strongest evidence of current maintenance weakness.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible community adoption adds modest uncertainty alongside the inactive commit history.
Composer is used for the build, but no security scanning tools are configured. For a payments client, the missing security tooling is a meaningful transparency and maintenance gap.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package handling payment integrations.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.9|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 10 months 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.