One registry publisher and no security policy leave limited visible ownership and disclosure support. The README, tests, MIT license, matching repository, and release notes provide useful adoption context.
63%
Total Score
50
100
88
50
Only one registry account has publish access. Because the repository owner is an individual rather than an organization, this leaves a thin visible maintainer base.
The package has existed for about 17 months with 7 releases, but only 1 release in the last 12 months; the history shows some maturity alongside slower recent delivery.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, indicating a meaningful maintenance slowdown and some abandonment risk.
There were 0 new or closed issues and pull requests in the last month, while 10 issues and 4 pull requests remain open; this suggests limited recent project follow-through.
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 |
|---|---|---|
laravel/tinker Version ^2.10.1 | — | — |
backpack/basset Version ^1.3 | — | — |
laravel/framework Version ^12.7 | — | — |
livewire/livewire Version ^3.5 | — | — |
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.