wpdesk/wp-view

wpdesk/wp-view 2.1.4 appears usable and reasonably transparent: it has a long package history, a stable non-prerelease version, a current release, an unarchived repository owned by an organization, documented source files and tests, a matching repository, and no install-time lifecycle scripts. The main concerns are that repository commit and issue activity were absent over the last 3 months, the repository has no security policy or declared workflow token permissions, and the project has negligible visible popularity. These concerns warrant monitoring, but they do not outweigh the package's licensing, testing, release, and organizational backing evidence.

Latest 2.1.4

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last 3 months, a meaningful maintenance-activity gap despite the recent release and push timestamp.

Repo issue activity

There were no new or closed issues or pull requests in the last month and no open work items; this is not severe alone, but it offers little evidence of an active maintenance feedback loop.

Repo popularity

The repository has zero stars, forks, and watchers, which provides little external validation and modestly increases adoption uncertainty, though popularity is supporting rather than decisive evidence.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a security-hygiene gap that is relevant but not independently disqualifying.

Security policy

No repository security policy was found, reducing transparency around vulnerability reporting and handling.