The README, MIT license, small dependency set, and lack of install-time scripts make the package straightforward to inspect and integrate. Maintenance evidence is weak, with no commits in the last three months, no recent releases, and no security policy. Adopt only with a plan to replace or maintain it if Laravel or Twilio compatibility changes.
56%
Total Score
50
100
88
75
The registry namespace and repository owner are the same individual account, giving a clear ownership link but no organizational backing to offset the thin maintenance capacity.
The package has 11 releases since August 2016, but none in the last 12 months and the latest release was in April 2023. This is meaningful abandonment risk, though the repository remains active enough to avoid the most severe band.
The repository had zero commits and zero active maintainers in the last three months. This directly weakens confidence that defects or dependency changes will be addressed promptly.
Composer is used as the build tool, but no security-scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a package that handles Twilio credentials and phone lookups, this reduces transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twilio/sdk Version ^5.0|^6.0|^7.0 | — | — |
illuminate/support Version ^5.0|^6.0|^7.0|^8.0|^9.0|^10.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.