Package Health/larangular/web-service-client

larangular/web-service-client

The MIT license and matching, non-archived repository provide clear ownership and basic transparency. A very small project with one registry maintainer, no recent commits, and no security policy leaves maintenance capacity and long-term support uncertain.

Latest 0.2.0

Packagist

48%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in September 2020, nearly six years ago, and there were no releases in the last 12 months. The six-release history shows an established package but not current distribution activity.

Maintainers

Only one account has registry publish access, which creates a thin publishing base. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. A push in February 2025 shows the repository is not entirely abandoned, but it does not demonstrate current maintenance.

Repo tooling

Composer is used for the build, which is appropriate, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.

Security policy

The linked repository has no security policy. That makes vulnerability reporting and response expectations unclear for dependents.