The package includes tests, a changelog, and release notes, with two contributors sharing recent work. Its small user-owned project and missing security policy leave less organizational safety net.
76%
Total Score
83
100
83
50
The repository is owned by the same individual namespace as the package, so the source relationship is coherent. It is user-owned rather than organization-backed, leaving a smaller maintenance handoff path.
The package is young, with three releases over 265 days and a median interval of about 89 days. That is limited maturity evidence, but the latest release is recent and repository activity remains current.
The repository has one star and one fork, so there is little external adoption evidence. Popularity is only supporting evidence, and the active commits and complete package structure compensate for the small audience.
Composer build tooling is present, but no security-scanning tool was detected. That leaves a modest transparency and maintenance gap for a package handling payment integrations.
The repository has no security policy. This is a genuine disclosure-process gap, although it is partly offset by the repository's tests, release notes, and recent activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^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.