ecare/sms

The package has a clear README, a small coherent source tree, and modest dependencies without install-time scripts. Organization backing and an MIT declaration help, but testing and security-process coverage are limited.

Latest v1.0.2

Packagist

59%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases are recorded, both published within about three hours, and no later release activity is shown over the package's 184-day age. This leaves maintenance continuity unproven.

Repo commit activity

There were no commits and no active maintainers in the last three months. Given the package's young age, this is a meaningful lack of continuing maintenance evidence.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance-process gap, not evidence that the package is unsafe.

Security policy

The repository has no security policy. For a package that handles an SMS API token, the missing disclosure and reporting process lowers transparency.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Ecare SMS

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^8.0\|^9.0\|^10.0\|^11.0\|^12.0	—	—
guzzlehttp/guzzle Version ^7.0	—	—
illuminate/support Version ^8.0\|^9.0\|^10.0\|^11.0\|^12.0	—	—