It includes a substantial Laravel implementation, a README, and an MIT declaration. The main concern is that the last release and repository push were about 16 months ago, with no commits in the last 3 months; one maintainer and no security tooling add uncertainty.
55%
Total Score
50
50
83
88
Fourteen runtime dependencies, including several related packages from the same publisher, create meaningful coupling and maintenance exposure. The profile is not inherently unsafe, but it increases the effect of stale project maintenance.
Only one registry account has publish access. This is a thin publishing base for a package with many runtime dependencies, although the linked project is owned by the same individual.
The repository owner is the same individual as the registry namespace, and the repository owner is a user rather than an organization. This provides direct ownership alignment but limited organizational backing.
The package has 15 releases, but none in the last 12 months and the latest release was about 16 months ago. This indicates materially stale maintenance despite its prior release history.
There were no commits and no active maintainers in the last 3 months, consistent with the release gap and raising abandonment risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/ui Version * | — | — |
doctrine/dbal Version * | — | — |
guzzlehttp/guzzle Version ^7 | — | — |
wangta69/laravel-auth Version * | — | — |
wangta69/laravel-meta Version * | — | — |
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.