pessek/pessek_favicon

The package is small and clearly matched to its repository, with only two runtime dependencies and no install scripts. Its single-maintainer ownership and lack of security policy reduce continuity and transparency for long-term use.

Latest v3.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer account provides little redundancy if that person stops maintaining or publishing the package. The repository is user-owned, so no organizational backing is shown to compensate for the thin maintainer base.

Project backing

The source repository is owned by an individual user rather than an organization, and no broader project backing is shown. This reinforces the continuity concern from the single maintainer.

Release history

This is the only release, published about five years ago, with no releases in the last 12 months. That suggests limited ongoing maintenance, although a small, stable plugin may need few releases.

Repo popularity

The repository has zero stars and forks and one watcher, providing little community evidence or external review. Popularity is supporting evidence rather than a verdict, so this is a modest concern for a small plugin.

Repo tooling

Composer is used as a build tool, which fits the package ecosystem, but no security scanning tooling is reported. For this small plugin that is a hygiene gap rather than a severe risk.