diegocopat/laravel-repository-pattern
Documentation and licensing are clear, but the project has little supporting activity or security process. Keep the dependency pinned and expect to maintain it yourself if Laravel compatibility changes.
56%
Total Score
50
100
83
83
Health Score Breakdown
One registry account has publish access. Because the linked project is user-owned rather than organization-backed, this indicates a thin publishing base and limited redundancy.
The repository is owned by an individual account, not an organization. Combined with one registry maintainer, this suggests limited project backing rather than a broader maintenance team.
The package has had only one release, published about 394 days ago, with no releases in the last 12 months. That leaves compatibility and ongoing maintenance uncertain.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external signal of maturity or community support.
Composer is used for builds, but no security scanning tooling is present. The missing scanning is a modest transparency and maintenance-process gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Diego Copat |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/console Version ^10.0|^11.0 | — | — |
illuminate/support Version ^10.0|^11.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.