back1ng/sms-ru
MIT licensing, tests, and a clear README support adoption. One maintainer, no security policy, and limited project activity leave oversight and future support uncertain.
58%
Total Score
50
100
88
83
Health Score Breakdown
Only one registry publishing maintainer is listed, and the project is user-owned rather than organization-backed. This leaves limited visible publishing redundancy.
The package has had three releases, all clustered on 9 April 2025, followed by about 17 months without a release. This suggests a settled but potentially inactive project.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the wider absence of recent releases and raising support risk.
Composer build tooling is present, but no security-scanning tools are reported. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. For a package that handles SMS service credentials and network requests, this reduces the clarity of vulnerability reporting and response.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Eugeny Nosenko |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version ^6.0|^7.0|^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.