mergado/mergado-api-client
Tests, a README, release notes, and organization ownership provide useful maintenance and consumer support. The MIT license is present, though its manifest label conflicts with the detected license; no security policy or scanning is also documented.
58%
Total Score
67
71
83
Health Score Breakdown
The package has had no registry release for about 4 years, despite nine releases overall; this is a meaningful maintenance concern for a client library.
The artifact and repository contain an MIT license, but the manifest declares the package proprietary. That mismatch reduces transparency even though licensing evidence is present.
There were no commits or active maintainers in the last 3 months, consistent with a project whose registry releases have stopped and increasing abandonment risk.
No issues or pull requests were created or merged in the last month, while two issues and three pull requests remain open; this suggests limited recent maintenance activity.
Composer build tooling is present, but no security scanning tools are reported. That is a hygiene gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Samuel Hudec |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 | — | — |
league/oauth2-client Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 10 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.