pawnpay/merchant_api
The package includes tests, a substantial README, release notes, and a matching MIT license. Its small footprint and lack of a security policy reduce confidence for a payment API.
54%
Total Score
75
100
83
88
Health Score Breakdown
The latest registry release was about five years ago, with no releases in the last 12 months. That is a meaningful maintenance concern, although the repository was pushed later than the last release.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this points to weak current maintenance.
The repository has one star, no forks, and no watchers. Popularity is only supporting evidence, but these numbers provide little external validation.
Composer build tooling is present, but no security scanning tools were detected. For a payment API adapter, that leaves a modest transparency and assurance gap.
The repository has no security policy. That makes vulnerability reporting and response expectations less clear, especially for a payment integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 PawnPay |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version >=6.3 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 6 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.