amekusa/wpelib

The small dependency footprint and Composer build support straightforward use. Documentation, tests, security policy, and repository security scanning are absent, leaving maintenance and integration quality largely unverified.

Latest 0.4.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in May 2017, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed in April 2023, current development activity is not demonstrated.

Package scaffolding

The package contains no README, tests, or changelog, and the repository also reports no tests or changelog. These omissions make integration and maintenance harder, though they are less severe than the stale release history.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy small package, but these values provide no supporting evidence of community adoption or review.

Repo tooling

Composer is used as a build tool, which supports reproducible project structure, but no security scanning tools are configured. The missing scanning reduces transparency for a package with no recent release activity.