Package Health/mingyoung/guzzle-middleware

mingyoung/guzzle-middleware

Risky to adopt for a new project: the package has had no release or repository activity for about five years and contains only two files. It is not deprecated and has a declared MIT license, but its very small footprint and lack of tests or security process leave little evidence of ongoing maintenance.

Latest 0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Release history

There has been only one release, published about five years and seven months ago, with no releases in the last 12 months. This is strong evidence of an unmaintained package.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since its only release. No newer activity is provided to offset the abandonment concern.

Package file tree

Both the published artifact and repository contain only composer.json and one PHP source file. This may be a deliberately small middleware package, but the minimal tree provides limited transparency about its maintenance and validation.

Package scaffolding

The artifact has no README, tests, or changelog, and the repository also reports no tests or changelog. Missing tests and changelog can be normal for a tiny published artifact, but the absent README makes integration harder and leaves little consumer-facing documentation.

Repo tooling

The repository uses Composer, but no security scanning tools are reported. The simple package structure limits the significance of this gap, though it leaves maintenance safeguards unverified.