Healthy and suitable to depend on, with modest maintenance caveats. It has regular releases, an active organization-owned repository, matching source, tests, and no deprecation or unsafe workflow findings; recent work is limited to one contributor and the repository lacks a security policy.
78%
Total Score
67
100
94
80
All recent commit activity comes from one contributor. Organization ownership provides some handoff capacity, but the observed short-term contributor base is still concentrated.
Only one commit was recorded in the last 3 months, with one active maintainer. Releases remain regular, but recent source activity is thin and merits monitoring.
Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and monitoring gap rather than evidence that the package is unsafe.
The repository has no published security policy. That makes vulnerability reporting and response expectations less transparent for a package handling messaging credentials.
The CI workflow declares no top-level token permissions, and none of its jobs provide read-only permissions. This is weaker least-privilege hygiene, although no write permission or dangerous workflow pattern was observed.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twilio/sdk Version ^8.7 | — | — |
illuminate/queue Version ^11.0||^12.0||^13.0 | — | — |
illuminate/events Version ^11.0||^12.0||^13.0 | — | — |
illuminate/support Version ^11.0||^12.0||^13.0 | — | — |
illuminate/notifications Version ^11.0||^12.0||^13.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.