eighteen73/laravel-google-chat
Healthy and usable, with some early-project caveats. It has recent releases, active repository work, documentation, tests, and organization backing, but all recent commits come from one contributor and the repository lacks a security policy and explicit workflow token permissions.
76%
Total Score
88
100
94
80
Health checks
All 28 recent commits came from one contributor, creating a real continuity risk; organization ownership provides some ability to hand maintenance off, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users are given no documented process for reporting vulnerabilities or receiving security guidance.
Neither workflow declares top-level token permissions. No write permissions were observed, but explicit least-privilege settings would make CI behavior more transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 eighteen73 |
| Frank Dixon |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 || ^8.0 | — | — |
league/commonmark Version ^2.8 | — | — |
illuminate/support Version ^12.0 || ^13.0 | — | — |
illuminate/notifications Version ^12.0 || ^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 1 month ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.