tecdiary/sms

The MIT license, matching organization-backed repository, and clear README support adoption. There is no security policy, only one open issue, and little community activity, leaving maintenance and response capacity uncertain.

Latest 1.0.3

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in June 2018, with no releases in the last 12 months and only four releases overall. This long period without a new release is strong evidence of abandonment risk, although the package is not marked deprecated.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. The repository is not archived, but there is no observed recent maintenance to offset the inactivity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with one issue still open. This indicates limited recent project engagement, though the small project size makes the absence of frequent issues less decisive than the lack of commits.

Repo popularity

The repository has 6 stars, 4 forks, and 1 watcher, providing little evidence of broad community review or support. Popularity is supporting evidence rather than a verdict, but it does not compensate for the maintenance gap.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and response-capacity gap, especially for a package that sends messages through external gateways.