yakimka/laravel-notification-channel-turbosms
It has a clear MIT license, a useful README, repository tests, and no install-time scripts. The workflow audit found no dangerous patterns, though its two action references are unpinned and no security scanning is configured.
59%
Total Score
50
81
100
Health Score Breakdown
The package has had no registry release for about five years, with zero releases in the last 12 months. Its earlier nine-release history provides some maturity but does not offset the current staleness.
The repository shows zero commits and zero active maintainers during the last three months. A push in April 2025 shows it was not permanently abandoned, but current maintenance activity is absent.
Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance gap rather than evidence that the package is unsafe.
The single workflow was fully analyzed with no dangerous audit findings or untrusted-checkout paths. However, both action references are unpinned, which weakens build reproducibility; the missing top-level permissions block is acceptable here because no broad write permissions are declared.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 yakimka |
| JhaoDa |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version 5.1 - 5.8|^6.0|^7.0|^8.0 | — | — |
illuminate/notifications Version 5.1 - 5.8|^6.0|^7.0|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 9 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.