Laravel apps as microservices: signed RPC through contracts, ordered events with an outbox, and read-only copies of another service's rows.
58%
Total Score
caution
A brand-new v0.1.0 release has only one commit from one contributor, despite solid tests and documentation.
The repository owner is an individual user rather than an organization, and no broader project backing is shown. That makes the single-maintainer activity concentration more consequential.
This package is brand new, with one release published today and no established release cadence. That limits evidence of sustained maintenance, though it is not abandonment by itself.
All recent activity comes from one contributor with a 100% commit share. The repository owner is an individual, so there is no organizational backing shown to offset this concentration.
Only one commit was recorded in the last three months, from one active maintainer. Because the release is brand new, this shows limited history rather than confirmed abandonment, but it weakens maintenance confidence.
The repository has zero stars, forks, and watchers. For a package released today this is limited supporting evidence rather than a strong negative signal.
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.