Yuboto SMS API consumer
58%
Total Score
50
100
88
75
A single registry maintainer creates a thin publishing base and increases continuity risk, although the matching personal repository provides some compensating ownership evidence.
The registry namespace and repository owner match, but the project is backed by an individual rather than an organization, so there is limited evidence of institutional continuity.
Only two releases exist, and the latest was published nearly six years ago with no releases in the last 12 months. This is meaningful abandonment risk for a library tied to an external SMS API.
There were no commits and no active maintainers in the last three months, reinforcing that ongoing maintenance is currently inactive.
Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance gap, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version 2.25.2 | — | — |
guzzlehttp/guzzle Version 6.3.3 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.