eazysoft/eazy-http

Consumers get little context about how to use or evaluate it. The package structure is coherent, but the available project evidence does not support relying on it for ongoing maintenance.

Latest 0.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published nearly five years ago, with no releases in the last 12 months. That strongly suggests the package is inactive and raises abandonment risk.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but that does not compensate for absent recent work.

License

The package has no declared license, license file, or detected repository license file. This creates a material adoption and redistribution concern.

Package scaffolding

The package contains a README, but it is only 11 characters and provides no meaningful consumer guidance. Tests and a changelog are absent from the published artifact, which is normal packaging practice; the exact version does have a GitHub release.

Repo tooling

Composer is used for the build, which is appropriate, but no security-scanning tooling is present. This is a modest hygiene gap rather than evidence of a vulnerability.