The README still contains template text, and the repository has no security policy or scanning tools. Organization backing, repository tests, a changelog, and a matching source repository provide useful structure, but there is not yet enough release history to establish durability.
58%
Total Score
75
75
50
The package uses a post-autoload-dump install-time script, adding execution during Composer installation and therefore some supply-chain exposure, although this alone does not show unsafe behavior.
The package is only 31 days old and has one release, so there is little evidence of sustained maintenance or a dependable release pattern.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. Because the package is only 31 days old, this is limited evidence rather than proof of abandonment, but it provides no demonstrated ongoing activity.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for a package intended to run developer commands.
The linked repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a hygiene gap rather than evidence that the release is unsafe.
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.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.