lablnet/http-client

Release historydanger

The package has only two releases and none in the past six years; the long interval since the last release is a substantial abandonment concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the package's prolonged release inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, leaving a meaningful repository hygiene gap for an HTTP client.

Security policycaution

The repository has no security policy, which makes vulnerability reporting and maintenance expectations less transparent, especially for a network-facing client.