leomanu/laravel-users
Tests, documentation, and a matching repository support adoption. The single-maintainer project lacks a published security policy, while its repository shows little recent development activity.
58%
Total Score
50
100
88
83
Health Score Breakdown
Only one registry account has publish access. That is consistent with the repository being owned by an individual, but it leaves limited visible publishing redundancy.
The registry namespace and repository owner match, and the owner is an individual rather than an organization. This supports ownership consistency but offers limited organizational backing.
The latest release was nearly six years ago, and there were no releases in the last 12 months. This is a meaningful maintenance concern, although the package has a substantial history of 33 releases.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this raises maintenance and abandonment concerns.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 jeremykenedy |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravelcollective/html Version ^5.4|^5.5|^5.6|^5.7|^5.8|^6.0|^7.0|^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 9 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.