Documentation, repository tests, release notes, and a security policy make it easier to adopt responsibly. The project is new and lightly released, so long-term maintenance remains less proven.
82%
Total Score
83
100
94
67
A post-autoload-dump script runs during installation, so installation has executable package behavior rather than being purely passive. That is a modest supply-chain and installation-complexity concern, with no provided evidence that the script is unsafe.
The repository is owned by a personal GitHub account rather than an organization, so maintenance depends on a small individual-backed project. The two active contributors partly offset that limitation.
The package is only 36 days old with two releases, although the median interval is about two days and the latest release is recent. This supports active early development but leaves long-term maintenance unproven.
Both workflows were analyzed successfully with no audit findings, all five action references are pinned, and no untrusted checkout or script-injection paths were found. One workflow grants top-level write permissions, which is a mild hygiene concern but not severe without an untrusted trigger.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^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.