The package has clear usage documentation, a stable release, and a small runtime dependency surface. Nearly two years without a new release, minimal repository traction, and no security scanning or policy reduce confidence in continued maintenance.
61%
Total Score
50
100
83
75
The repository is owned by an individual account rather than an organization. That is not inherently unhealthy, but it provides less visible backing for long-term maintenance.
The latest release was nearly two years ago, and there were no releases in the last 12 months. That is meaningful evidence of slowing maintenance, although the package may be feature-complete.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of a broad active community.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance weakness, not evidence that the package is unsafe.
The repository has no security policy. For a small notification package this is a modest transparency gap, but it reduces clarity about vulnerability reporting.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.0|^9.0|^10.0|^11.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.