Validation rules and utilities for Laravel
78%
Total Score
healthy
Frequent releases and a current repository support adoption, despite all recent commits coming from one contributor.
The repository owner is an individual user rather than an organization, so the concentrated recent commit activity is not offset by visible organizational handoff capacity.
One contributor made all 20 recent commits, leaving no demonstrated backup maintainer and increasing continuity risk if that contributor becomes unavailable.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide little independent validation of project adoption.
Composer is used for builds, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap, not evidence of unsafe code.
The repository has no security policy, so its process for reporting and handling vulnerabilities is unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/validation Version ^v13.35.0 | — | — |
aedart/athenaeum-utils Version ^10.22 | — | — |
aedart/athenaeum-support Version ^10.22 | — | — |
aedart/athenaeum-contracts Version ^10.22 | — | — |
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.