Guarded tools and assurance tests for Laravel AI agents: workspace isolation, honest failures and evidence on every tool call.
68%
Total Score
caution
A very new package has no established maintenance history, while every workflow action reference is unpinned.
The registry namespace and repository owner match, but the owner is an individual rather than an organization, so the project has a narrow visible backing structure.
The package was first released less than one day ago and has already had 7 releases, with a median interval of about 2 hours. This shows active initial development but provides no long-term release history yet.
The repository records 0 commits and 0 active maintainers in the last 3 months. Because the package is less than one day old, this is partly expected, but it leaves maintenance capacity unproven.
The repository has 0 stars, forks, and watchers. This is weak supporting evidence, but the package's less-than-one-day age makes low visibility expected rather than decisive.
No security policy was found in the repository. This is a transparency gap, though it is less concerning for a package with no established long-term history than an archived or deprecated project would be.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework 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.