ekstremedia/laravel-yr
Clear licensing, tests, and recent releases make the package easier to adopt. Maintenance depends on one contributor, and the workflow should pin its four external actions before relying on it widely.
70%
Total Score
63
100
94
67
Health Score Breakdown
Only one registry account has publish access. Because the repository owner is an individual rather than an organization, this reinforces the project's limited continuity capacity.
The repository is owned by a User account, not an organization, so there is no shown organizational backing to offset the concentrated contributor base.
One contributor made all three commits in the last three months, leaving no demonstrated backup maintainer and increasing abandonment risk if that contributor becomes unavailable.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence of a specific defect.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for users of this integration package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Terje Nesthus |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 10 months 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.