Package Health/fardadev/kavenegar-for-laravel

fardadev/kavenegar-for-laravel

Repository tests, documentation, and licensing provide a solid base. The absence of commits for three months and weak workflow controls make ongoing maintenance and release safety less reassuring; pin this beta rather than floating it.

Latest v1.0.0-beta.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers during the last three months. Although a recent release exists, the lack of current commit activity lowers confidence in ongoing maintenance.

Repo issue activity

The repository has three open pull requests and one open issue, but no issues or pull requests were opened or closed during the last month. This suggests limited recent project interaction.

Security policy

The repository has no security policy. For a package integrating an external SMS API, this is a transparency and vulnerability-reporting gap.

Version stability

The assessed release is a beta and two-thirds of recent releases are prereleases, indicating an immature API and greater change risk than a stable major release.

Workflow audit

All 12 action references are unpinned, three workflows grant top-level write permissions, and a high-confidence bot-conditions finding affects the Dependabot auto-merge workflow. The pull_request_target trigger has no untrusted checkout or script-injection sink, so this is a meaningful hygiene concern rather than a severe standalone risk.