Version 3.3.1 appears healthy and reasonable to depend on: it is a stable, non-deprecated release with 22 releases over 455 days, 17 releases in the last 12 months, a recent repository push, documented licensing, repository tests and changelog coverage, and modest dependency complexity. The main risks are operational rather than abandonment-level: all recent commits come from one contributor, the package has very limited popularity, and several workflows grant write permissions or use pull_request_target. The package is therefore suitable for adoption with normal dependency and CI review, but it has less maintainer redundancy and repository security hardening than a mature, widely backed project.
82%
Total Score
70
100
94
70
Five workflows were analyzed; one uses pull_request_target, which can be a sensitive workflow context. No untrusted checkout or script-injection patterns were detected, reducing but not eliminating the workflow risk.
The package uses a post-autoload-dump lifecycle script. This is an install-time execution surface that warrants review, although the signal does not show multiple or obviously excessive lifecycle hooks.
Only one account has registry publish access. This is a limited publishing redundancy signal, and the repository evidence also shows a single active contributor, so release continuity depends heavily on one person.
The repository owner is the individual user bnussbau, not an organization. This does not indicate poor health by itself, but it means the single-maintainer and bus-factor concerns are not visibly mitigated by organizational backing.
One contributor made all 6 commits in the last 3 months, with a 100% commit share. Because the owner is an individual user rather than an organization, there is no provided project-backing evidence to compensate for this concentration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^10.0||^11.0||^12.0||^13.0 | — | — |
spatie/laravel-package-tools Version ^1.18 | — | — |
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.