guzzlehttp/log-subscriber

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement provided. This is a direct adoption risk because future fixes and compatibility work should not be expected.

Release historydanger

The package has only three releases, with the latest published in October 2014 and none in the last 12 months. That long release gap strongly indicates abandonment for a dependency intended to integrate with evolving HTTP and logging ecosystems.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months. This is consistent with the archived repository and materially increases the risk that issues will remain unresolved.

Repository archiveddanger

The linked repository is archived and was last pushed in May 2016, indicating that active maintenance has ended. The organization backing and package-repository name match confirm the repository is relevant but do not compensate for its archived status.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are reported. The missing scanning is a secondary hygiene gap; the decisive concerns are deprecation and abandonment.