uconn/uconn-banner-wp

Clear installation guidance, a matching repository, and a documented release make adoption straightforward. MIT licensing and organization ownership add transparency, but the project lacks recent maintenance and visible security safeguards.

Latest v1.2.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with roughly 7 years since the last push. This is the strongest evidence of abandonment risk.

Lifecycle scripts

A post-install Composer script adds install-time behavior that consumers must trust. No provided signal explains or compensates for that behavior, so it is a modest supply-chain hygiene concern.

Release history

This is the package's only release, published about 9 years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite the stable version label.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. That weakens maintenance and release oversight for an old plugin.

Repository archived

The repository is not archived, which is positive, but it was last pushed about 7 years ago. The inactivity is a maintenance concern, also reflected in the commit activity signal.