Usable with caveats: the package is clearly licensed, documented, actively published, and backed by a matching repository. Its two-release history, single maintainer, absent recent commit activity, and lack of tests or security policy make long-term maintenance less certain.
62%
Total Score
67
100
89
90
Only one registry maintainer is listed. That is consistent with the individually owned repository, but it leaves little visible publishing redundancy if that maintainer becomes inactive.
Only two releases exist across about 290 days, so the project has limited demonstrated release maturity and cadence.
The repository recorded zero commits and zero active maintainers during the last three months. Although it was pushed recently, the available history still provides weak evidence of sustained maintenance.
The repository has zero stars, forks, and watchers. This does not make a small package unsafe, but it offers no supporting evidence of broad community adoption or review.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a package that handles API integrations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^7.0|^8.0|^9.0|^10.0|^11.0|^12.0|^13.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.