Laravel validation rule that checks if a password has been exposed in a data breach
68%
Total Score
caution
Usable with caveats: one contributor owns all recent commits and both workflow actions are unpinned.
The repository is owned by an individual user rather than an organization, so the single-contributor concentration is not visibly offset by organizational backing.
One contributor made 100% of the recent commits, leaving maintenance dependent on a single person with no provided evidence of an active backup contributor.
Only one commit was recorded in the last 3 months, indicating limited recent development activity despite the package's recent release history.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^8.0||^9.0||^10.0||^11.0||^12.0||^13.0 | — | — |
jord-jd/password_exposed Version ^5.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.