Documentation, tests, licensing, and a clean package layout make integration straightforward. Maintenance has been inactive for over four years at the registry and over three years in the repository, while the lone maintainer and unpinned workflow actions add smaller concerns.
54%
Total Score
25
100
86
67
The package has made no release in over four years, despite seven releases across its lifetime; this is substantial evidence of stalled maintenance.
There were zero commits and zero active maintainers in the last three months, consistent with a repository whose last push was over three years ago and raising abandonment risk.
One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing capacity when combined with the long period of inactivity.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this is a transparency gap for a package handling notification credentials.
The single workflow was fully analyzed with no dangerous audit findings, but both of its two action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.0|^7.0|^7.2 | — | — |
illuminate/support Version ^6.0|^7.0|^8.0|^9.0 | — | — |
illuminate/notifications Version ~5.8.0|^6.0|^7.0|^8.0|^9.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.