The artifact is well documented, licensed, and backed by repository tests, while the repository has no security tooling or policy. Its single-maintainer, zero-popularity profile leaves little evidence of resilience beyond the initial release.
62%
Total Score
50
100
75
75
One registry maintainer is consistent with an independently owned package, but it also indicates limited publishing redundancy for a package with no demonstrated history.
The package is 0 days old with only 2 releases, so there is not yet enough history to demonstrate sustained maintenance or release reliability.
The repository has 0 commits and 0 active maintainers in the last 3 months; because the package is brand new, this is limited evidence rather than proof of abandonment, but it leaves maintenance capacity untested.
The repository has 0 stars, forks, and watchers. Popularity is only supporting evidence, but this provides no external resilience or adoption signal for the new package.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
laravel/framework Version ^12.18|^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.