The lone maintainer and absent security safeguards leave limited evidence of long-term support. Repository tests, a clear README, and an MIT license improve adoption confidence.
58%
Total Score
33
100
83
75
The repository recorded zero commits and zero active maintainers in the last three months; for a package released only a few months ago, this is a meaningful maintenance concern.
A single registry publishing account provides little redundancy, and the backing repository is owned by a user rather than an organization.
The registry and repository are backed by the same individual user account, with no organization backing shown; this provides limited continuity if that maintainer becomes unavailable.
The package is only 121 days old and has two releases, both within the first week; this is too little history to demonstrate sustained maintenance.
The repository has zero stars, forks, and watchers, offering no supporting evidence of community review or adoption; this is secondary to the maintenance signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
laravel/framework Version ^10.0 || ^11.0 || ^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.