Usable with caveats: it has frequent stable releases, clear documentation, tests, licensing, and organizational backing. However, no commits were recorded in the last three months, and the repository has no security policy or scanning tools.
65%
Total Score
75
100
89
75
No commits and no active maintainers were recorded in the last three months. This conflicts with the strong release history and recent repository push, but it remains a meaningful warning about whether ongoing source development is visible.
The repository has zero stars, forks, and watchers after more than a year. Organizational backing and the package's active release history compensate partly, so this is supporting caution rather than a decisive abandonment signal.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap, though it is not by itself evidence that the package is unsafe.
The linked repository has no security policy. For a package containing authentication, permissions, tenancy, and API functionality, the lack of documented vulnerability-reporting guidance is a real transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
stancl/tenancy Version ^3.9 | — | — |
laravel/sanctum Version ^4.0 | — | — |
laravel-lang/lang Version ^15.0 | — | — |
laravel/framework Version ^12.0 | — | — |
barryvdh/laravel-dompdf Version ^3.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.