The single-maintainer project is very young, with three releases clustered within minutes and no commits during the last three months. MIT licensing, a strong README, repository tests, a changelog, and Dependabot provide useful structure, but the workflow audit also found a high-confidence bot-condition problem.
55%
Total Score
25
86
50
The repository recorded zero commits and zero active maintainers during the last three months, a meaningful warning for a package that is still early in its lifecycle.
The repository is owned by an individual rather than an organization, so the single registry maintainer corresponds to a thin project backing and leaves limited redundancy if the owner becomes inactive.
The package is only 166 days old, and all three releases arrived within minutes, so there is little evidence of a sustained release track record.
No security policy is present, which limits the documented route for reporting vulnerabilities; this is a transparency gap but not evidence of abandonment by itself.
Version v0.1.2 is not at a stable major version, which indicates an early API and maintenance stage rather than a mature dependency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
livewire/livewire Version ^4.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.