Token authentication for service-to-service calls between Laravel apps, with per-route permissions and an interactive manager.
58%
Total Score
caution
A first-day v0.1.0 release has no track record or commit history, with one maintainer and no repository security tooling.
The registry lists one maintainer, which creates a thin publishing base and some continuity risk. The linked repository is user-owned rather than organization-backed, so no broader maintainer capacity is shown.
This is the package's first release, published 0 days ago, with only one release and no established release cadence. Its recency explains the lack of history but does not yet demonstrate sustained maintenance.
The repository has 0 commits and 0 active maintainers in the past 3 months, although the package and repository were created today. This is consistent with a new project but provides no evidence of ongoing maintenance yet.
Composer build tooling is present, but no security scanning tools were detected. For a package handling service authentication tokens, this is a meaningful transparency and maintenance gap.
The repository has no security policy. That leaves reporting and response expectations unclear for a package implementing authentication controls.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.26 || ^13.0 | — | — |
elyar/personal-laravel-helpers Version ~0.0.1 | — | — |
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.