loglia/laravel-client

Risky to adopt for a new project: the package has had no release or repository commit activity for more than five years. It is not deprecated or archived, and the repository has tests and a clear package match, but the long-standing inactivity creates substantial maintenance risk.

Latest v3.1.0

Packagist

45%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published more than five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk despite a history of 27 releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no visible ongoing maintenance.

Repo tooling

The repository uses Composer build tooling, but no security-scanning tools were detected. This modestly limits automated security hygiene evidence without indicating that the package is unsafe.

Security policy

The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, although it is secondary to the much larger maintenance concern.

Token permissions

The repository workflow does not declare top-level token permissions. No write permissions or dangerous workflow patterns were observed, so this is a limited CI hygiene concern rather than a severe risk.