Usable with caveats: the package is licensed, documented, tested, and backed by a matching organization repository, but its latest release was about nine years ago and repository commits stopped about six years ago. Depend on it only if its old Laravel and provider integrations remain suitable for your project.
55%
Total Score
50
50
83
90
The package has 15 releases and a historically regular median interval of about 37 days, but there have been no releases in the last nine years. That long release gap is a significant maintenance concern.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having been inactive for about six years. This materially raises abandonment and compatibility risk.
Nine runtime dependencies, including several Laravel components and provider SDKs, create a relatively broad compatibility surface. This is a manageable concern for a provider-integration package but increases the cost of relying on an old release.
Only two issues are open and no recent issues or pull requests were recorded. The low workload is not inherently negative, but it also shows no recent maintenance activity.
Composer build tooling is present, but no security scanning tools were detected. For an older package with no recent development, the absence of automated security checks is a transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twilio/sdk Version ~4 | — | — |
illuminate/log Version >=5.0.0 | — | — |
illuminate/mail Version >=5.0.0 | — | — |
illuminate/view Version >=5.0.0 | — | — |
plivo/plivo-php Version ^1.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.