coercive/imgprocess

Usable with caveats: it is licensed, documented, not deprecated, and backed by a matching repository, but maintenance appears slow. There have been no releases in about 17 months and no commits in the last three months, while the very small repository lacks tests and security scanning.

Latest 0.1.2

Packagist

61%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The package and repository each contain only eight files, with implementation concentrated in dist/ and no visible test suite or broader project structure. This is a modest transparency and maintainability concern for a library dependency.

Release history

The package has existed since 2017 with 17 releases, but it has had no release in about 17 months. That weakens evidence of current maintenance despite the long history.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Although the latest registry release was accompanied by a repository push, current maintenance capacity is not demonstrated.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence that the package is unsafe.

Version stability

Version 0.1.2 is not marked as a prerelease, but the 0.x version line still indicates a less mature stability commitment than a stable major release.