The package is clearly tied to its source repository, with a focused dependency set and a useful README. Limited testing and absent security-policy coverage leave less evidence for long-term maintenance.
67%
Total Score
50
100
89
83
Only one registry account has publish access. Because the source repository is user-owned rather than organization-backed, this indicates a thin publishing and continuity base.
The package and repository are consistently owned by the same individual account, which supports provenance but provides no organizational backing to offset the single-maintainer structure.
There were no commits and no active maintainers in the last three months. The recent release partly offsets this, but the current maintenance capacity remains unclear.
The repository has one star and one fork, indicating very limited adoption evidence. Popularity is supporting evidence, so this lowers confidence in project maturity but is not decisive alone.
Composer build tooling is present, but no security scanning tools were detected. This is a modest repository-hygiene gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.92 | — | — |
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.