The README and changelog make integration straightforward, and releases have arrived regularly since January 2026. Maintenance depends on one contributor, while both workflow actions are unpinned and the repository has no security policy or scanning tools.
68%
Total Score
50
100
88
75
All 3 recent commits came from one contributor, whose commit share is 100%. This concentrates maintenance responsibility and raises abandonment risk.
The repository recorded 3 commits in the last 3 months, showing some recent activity. The volume is modest, so it provides only moderate maintenance evidence.
The repository has 0 stars, forks, and watchers. This is weak supporting evidence, but the package is only about 260 days old and popularity alone does not establish poor health.
Composer is used for builds, but no security scanning tools are detected. That is a transparency and maintenance gap for a package handling authentication tokens.
The repository has no security policy. For a package implementing email, SMS, and two-factor token flows, the absence of a documented vulnerability-reporting path is a meaningful transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.10 | — | — |
pragmarx/recovery Version ^0.2.1 | — | — |
illuminate/support Version ^12 | — | — |
pragmarx/google2fa-laravel Version ^3.0.1 | — | — |
laravel/vonage-notification-channel Version ^3.3 | — | — |
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.