The README, changelog, tests, and MIT license provide useful transparency. A single maintainer, no security policy, and minimal repository activity leave substantial maintenance risk.
38%
Total Score
25
100
75
75
The package has had only two releases, both in October 2020, with no releases in the last 12 months and roughly six years since the latest release. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no visible ongoing maintenance.
Only one account has registry publish access. That creates a thin publishing base, although the linked repository and package appear consistently owned by the same individual.
The repository has zero stars and forks and only one watcher. Popularity is not decisive by itself, but these counters provide no supporting evidence of broad adoption or community attention.
The linked repository has no security policy. For a Laravel package that handles scheduled outbound requests, this is a transparency gap, though it is less severe than the inactivity evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.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.