bnomei/kirby3-posthog

Documentation, licensing, and repository/package alignment are solid. A single maintainer, no commits in three months, and unpinned workflow actions leave meaningful maintenance and build-hygiene risk; pin 5.3.0 if adopting.

Latest 5.3.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access. That is a meaningful bus-factor concern for a user-owned project, although registry access alone does not establish whether other contributors maintain the code.

Project backing

The registry namespace and repository are owned by the same individual, so the package has clear ownership, but there is no organization backing to compensate for its single-maintainer structure.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Although a release was published during the broader period, the lack of recent development activity lowers maintenance confidence.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher. Low popularity is supporting evidence rather than a verdict, but it provides little external adoption or review signal.

Repo tooling

Composer is used for builds, but no security-scanning tooling is present. The missing scanner is a hygiene gap rather than evidence that the release is unsafe.