The package includes tests, a changelog, release notes, and a focused dependency set. Its install-time script and lack of security scanning or a security policy leave some hygiene gaps.
67%
Total Score
50
100
93
50
The package uses a post-autoload-dump install lifecycle script. This is a supply-chain and installation-hygiene consideration, though the signal does not show that the script performs harmful actions.
The package and repository are owned by the same individual account. That is coherent backing, but it also indicates a single-person ownership model rather than organizational resilience.
No commits and no active maintainers were recorded during the last three months, which is a maintenance concern. Frequent recent registry releases and four merged pull requests in the last month partly offset that gap, so this is caution rather than danger.
Composer is used as the build tool, but no security-scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. This reduces transparency about how vulnerabilities are reported and handled, though it does not establish abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.0 || ^13.0 | — | — |
spatie/laravel-data Version ^4.17 | — | — |
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.