mupaybr/mupay-sdk
Usable with caveats: it has a clear README, tests, release notes, active recent commits, and organization backing. However, it is a young v0 package with only two releases, all recent work from one contributor, and no security policy or scanning.
72%
Total Score
88
100
78
90
Health Score Breakdown
The package is only 113 days old and has two releases, with a median interval of about 101 days. That is limited history for judging long-term maintenance, so adoption carries some maturity risk.
One contributor made all 56 commits in the last three months, creating a real continuity risk. The organization-owned repository provides some ability to hand maintenance to others, so this is caution rather than severe risk.
The repository has zero stars, forks, and watchers. This does not prove poor quality, but it provides no supporting evidence of external adoption or review.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning reduces supply-chain transparency for a payment SDK.
The repository has no security policy. For an SDK handling payment integrations, this is a meaningful disclosure and maintenance gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 MuPag |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^1.1 || ^2.0 || ^3.0 | — | — |
psr/http-client Version ^1.0 | — | — |
psr/http-message Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^7.9 | — | — |
Weekly Downloads
Info
- Last Published
- 22 days ago
- Created
- 4 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.