goletter/hyperf-sms
The MIT license, focused dependency set, README, and package-to-repository match provide a clear adoption baseline. The missing security policy and minimal project activity leave maintenance and operational transparency weaker than established dependencies.
58%
Total Score
50
100
83
88
Health Score Breakdown
The repository is owned by the same individual account as the registry namespace. This confirms alignment, but it does not provide organization-level maintenance backing.
All five releases were published within about 6 minutes on the first release day, with no later release activity across nearly 11 months; this suggests an initial burst rather than an established cadence.
There were no commits and no active maintainers in the last three months, which is a concrete sign of limited ongoing maintenance for a package released nearly 11 months ago.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external adoption signal to offset the inactivity.
Composer is used as the build tool, but no security-scanning tools are configured, leaving a modest transparency and maintenance gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 goletter |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/di Version ~3.1.0 | — | — |
guzzlehttp/guzzle Version ^7.10 | — | — |
Weekly Downloads
Info
- Last Published
- 11 months ago
- Created
- 11 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.