fize/provider-sms
The MIT license, consumer README, and release notes provide basic transparency. The remaining evidence leaves maintenance and package provenance uncertain.
48%
Total Score
50
63
75
Health Score Breakdown
Only one release exists, published about 6 years ago, with no releases in the last 12 months. This provides little evidence of sustained release maintenance.
The repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less transparent and raises provenance concern.
There were no commits and no active maintainers in the last 3 months. This conflicts with the recent push timestamp and leaves current development activity weakly evidenced.
Composer build tooling is present, but no security scanning tools were detected. This is a modest repository-hygiene gap, not evidence of unsafe code by itself.
The repository has no security policy. For a package that sends SMS and depends on external service libraries, this weakens vulnerability-reporting transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 FizeChan |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 fize/crypt Version ~3.2 | — | — |
alibabacloud/client Version ~1.5 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 6 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.