milwad/laravel-validate
It has clear licensing, release notes, active recent commits, and a matching repository with tests. Treat the automated merge workflow as a maintenance and release-process concern, and expect most changes to depend on one contributor.
68%
Total Score
67
100
100
75
Health Score Breakdown
The repository is owned by an individual user rather than an organization, so the concentrated recent contribution pattern is not visibly compensated by organizational backing.
Two contributors were active, but one made 10 of 11 recent commits, leaving maintenance heavily concentrated despite the second contributor's activity.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. Other provided tooling, including Dependabot, partly offsets this transparency gap.
All five workflows were analyzed, but the audit found a high-confidence bot-conditions issue in the Dependabot auto-merge workflow, and all nine action references are unpinned. A pull_request_target trigger has no untrusted checkout or script-injection sink, so the trigger alone is not dangerous, but the workflow hygiene still weakens release-process confidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Milwad Khosravi |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/framework Version 9.*|10.*|11.*|12.*|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 3 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.