lianmaymesi/laravel-backend
MIT licensing, a substantial README, repository tests, and release notes improve transparency. Workflow permissions and unpinned actions add maintenance overhead, while the single maintainer limits resilience.
58%
Total Score
50
92
50
Health Score Breakdown
Registry publishing is handled by one maintainer. The repository is user-owned rather than organization-backed, so there is little visible publishing redundancy if that maintainer becomes unavailable.
The package has 118 releases since November 2023, but none in the last 12 months; that recent pause raises maintenance concerns despite the historically active release cadence.
The repository recorded zero commits and zero active maintainers in the last 3 months, a concrete sign of currently limited maintenance activity.
There are six open pull requests, with no new or merged pull requests in the last month, suggesting contributions are not currently being processed actively.
The linked repository has no security policy, leaving no documented path for reporting vulnerabilities or coordinating fixes.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Lian Dhas I M |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 livewire/livewire Version ^3.6 | — | — |
illuminate/contracts Version ^12.0 | — | — |
spatie/laravel-package-tools Version ^1.14.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 2 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.