The package has a clear README, MIT licensing, repository tests, and workflows without dangerous trigger or checkout patterns. Its security policy is missing, and workflow permissions are broader than necessary, adding maintenance and governance concerns.
58%
Total Score
50
88
63
The package uses a post-autoload-dump Composer lifecycle script. This is a meaningful installation-time behavior to understand, but the signal alone does not show that it is unsafe.
The repository is owned by an individual account rather than an organization, so there is no organizational backing shown to compensate for a thin maintainer base.
All 11 releases were published on the same day, clustered within about five minutes, with no later release activity over roughly nine months. This leaves the longer-term maintenance pattern unproven.
There were no commits and no active maintainers in the last three months. Combined with the release history, this is a concrete sign that ongoing maintenance has not been demonstrated.
Composer build tooling is present, but no security scanning tools were detected. That is a governance 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 | — | — |
egulias/email-validator Version ^4.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
propaganistas/laravel-disposable-email Version ^2.0 | — | — |
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.