Disable personal teams in Laravel Jetstream
58%
Total Score
caution
Usable with caveats: maintenance has been inactive for about two years.
The package has four releases, but none in the last 12 months; its latest release was about two years ago. The earlier short release intervals show some initial activity but do not offset the current pause.
There were no commits and no active maintainers in the last three months, consistent with the roughly two-year release gap. For a package tied to changing Laravel and Jetstream versions, that weakens confidence in ongoing compatibility maintenance.
The repository has one star, zero forks, and one watcher, providing little evidence of a broad user or contributor base. Popularity is only supporting evidence, but this adds to the limited maintenance-capacity concern.
Composer build tooling is present, but no security scanning tooling was detected. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a small middleware package this is a hygiene gap, but it is less significant than the inactive maintenance signal.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version >=10.0 | — | — |
spatie/laravel-package-tools Version >=1.14.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.