Define your CI/CD pipeline once in config/slipway.php and compile it to GitHub Actions, Bitbucket Pipelines and GitLab CI.
67%
Total Score
caution
A brand-new package with four releases in one day has not yet demonstrated sustained maintenance.
The package runs a post-autoload-dump install-time script. This is a supply-chain and installation-behavior consideration, although the signal does not show that the script is malicious.
Only one registry maintainer is listed, so continuity depends heavily on a single person; the linked repository is also owned by an individual rather than an organization.
The repository and registry are owned by the same individual account, which supports identity consistency but does not provide organizational continuity.
The package is only 0 days old, with four releases all published within roughly 2 hours; this shows active initial publishing but provides no sustained maintenance track record.
There were zero commits and zero active maintainers in the preceding 3 months, but the package is 0 days old, so this is primarily a lack of history rather than evidence of a recent collapse.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^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.