Usable with caveats: the package is licensed, documented, tested, and backed by a matching repository with a stable release. The main concern is that the repository has had no commits or active maintainers in the last three months, with only one publisher and no security scanning or policy.
66%
Total Score
67
100
89
75
Only one account has registry publish access. That is a meaningful continuity concern for a user-owned project because release availability depends on one person.
The repository recorded zero commits and zero active maintainers in the last three months. This is the strongest concern because it may indicate that maintenance has slowed after the latest release.
The repository has five stars, no forks, and one watcher. This is limited adoption evidence, but popularity is supporting context rather than a health verdict and does not outweigh the package's concrete documentation and tests.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces assurance for a package handling authentication and push-notification integrations.
The repository has no security policy. This weakens transparency about vulnerability reporting and handling, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
google/auth Version ^1.42 | — | — |
illuminate/http Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/notifications Version ^10.0|^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.