The package has only two releases and no automated tests or security scanning. Its organization-owned repository and clear README provide useful context, but maintenance evidence remains thin.
61%
Total Score
88
100
89
75
Only two releases have been published over about six months, with the latest release roughly five months ago. This is a young project with limited evidence of sustained maintenance.
There were no commits and no active maintainers during the last three months. Combined with the short release history, this is the clearest evidence of limited ongoing maintenance.
Composer is used as the build tool, but no security-scanning tools are configured. The missing scanning is a hygiene weakness rather than evidence that the package is unsafe.
The repository has no security policy. For a package that handles API credentials and sends messages, this reduces transparency around vulnerability reporting and response.
No GitHub Actions workflows were present, so there were no workflow risks or unpinned actions to flag. This also means the repository provides no workflow-based evidence of automated validation or release hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.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.