Idempotency keys for Laravel side effects: an atomic once() and the claim, complete and completed primitives, backed by one unique index.
68%
Total Score
caution
A well-documented first release with good project structure, but little maintenance history and weak workflow pinning.
The package runs a post-autoload-dump install-time script. The signal does not show that it is unsafe, but lifecycle execution adds a small supply-chain and installation-review concern.
This is the package's first release and it is only hours old, so there is no demonstrated release track record yet. The age is too short to treat the absence of later releases as abandonment.
Composer build tooling is present, but no security scanning tool was detected. For a newly published library this is a modest transparency and assurance gap.
The repository has no security policy. This is not evidence of unsafe code, but it gives maintainers and consumers no documented vulnerability-reporting path.
The workflow audit completed cleanly with no dangerous triggers, untrusted checkouts, or high-confidence findings, but all four action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/database Version ^12.0|^13.0 | — | — |
illuminate/contracts Version ^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.92 | — | — |
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.