Package Health/aaemnnosttv/wp-cli-media-generate-command

aaemnnosttv/wp-cli-media-generate-command

The package is clearly identified, licensed, documented, and has a small dependency footprint. Its maintenance record is the main concern: only two releases exist, none in the last 12 months, and no maintainers committed in the last three months.

Latest v1.0.1

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, with the latest released in July 2017 and none in the last 12 months. That long release gap materially raises abandonment and compatibility risk.

Project backing

The repository is owned by an individual rather than an organization, so there is no organizational maintenance capacity to offset the thin activity record.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates very limited current maintenance capacity.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a small, dormant project, but does not by itself prove abandonment.

Repo tooling

The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a hygiene limitation rather than a severe dependency risk.