mubeen/laravel-user-crud
Tests, a usable README, and an MIT declaration provide a reasonable foundation, and the repository is not archived. The single-maintainer presentation and absent security policy reduce confidence for a framework integration.
53%
Total Score
50
100
83
75
Health Score Breakdown
Only one registry publishing account is listed, named “Your Name.” For an individually owned project this is a modest maintainability concern, especially alongside the sparse release history.
The repository is owned by an individual account rather than an organization. That is consistent with a small personal project and gives no additional organizational maintenance backing.
The package has only two releases, both published within about 25 minutes, and none in the last 12 months despite being 523 days old. This is strong evidence of limited maintenance and maturity.
The repository has zero stars and forks and one watcher. Popularity is not required for a healthy small package, but these counters provide little supporting evidence of maturity or community adoption.
Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and hygiene gap rather than evidence that the release is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Your Name |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/auth Version ^12.0 | — | — |
illuminate/support Version ^12.0 | — | — |
illuminate/database Version ^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.