Agent-focused request profiler for Laravel with an MCP server: timing spans, queries, cache, filesystem, AI agent calls and more.
62%
Total Score
caution
A brand-new package has rapid releases, one contributor, and all 16 workflow actions are unpinned.
A post-autoload-dump install-time script runs during Composer installation, adding execution complexity for consumers. The signal provides no evidence that the script is unsafe, so this is a limited supply-chain caution.
Only one account has registry publish access. That is a small publishing base, and the repository evidence also shows one active contributor, so there is limited demonstrated maintenance redundancy.
The registry namespace and repository are owned by the same individual account, not an organization. This matches the single-contributor evidence and provides no additional handoff capacity.
The package is less than a day old, with nine releases in about 13 hours and a median interval of roughly 42 minutes. This shows active initial development but gives little evidence of sustained maintenance.
One contributor made all 40 commits in the last three months, giving the project a complete single-contributor concentration. The repository owner is an individual, so no organizational backing compensates for this bus-factor risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/mcp Version ^1.0 | — | — |
laravel/boost Version ^2.10 | — | — |
illuminate/support Version ^13.0 | — | — |
illuminate/contracts Version ^13.0 | — | — |
laravel/agent-detector Version ^2.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.