coopxl/tapayment
The MIT license, readable documentation, stable version, and lack of install-time scripts make integration straightforward. A single publisher, no security policy, and a very small repository reduce transparency and long-term confidence.
62%
Total Score
67
100
83
83
Health Score Breakdown
Only one account has registry publish access, leaving little publishing redundancy. This is a modest transparency and continuity concern, though access records do not prove who actively maintains the code.
The repository is owned by an individual account rather than an organization, and the registry namespace differs from that account. This offers limited institutional backing, while the provided ownership data does not establish abandonment.
All five releases were clustered on February 9, 2025, and there have been no releases in about 19 months. That provides a concrete maintenance concern for a payment integration.
The repository has zero stars and forks and one watcher. Popularity is not required for health, but these counters provide little supporting evidence of community adoption or review.
The repository uses Composer, which fits the package ecosystem, but it reports no security-scanning tooling. That is a minor process gap rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Hossam hassan |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.7|^8.0 | — | — |
illuminate/support Version ^8.0|^9.0|^10.0|^11.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.