Package Health/johannschopplich/kirby-deploy-trigger

johannschopplich/kirby-deploy-trigger

It has clear documentation, a stable version, and a small dependency footprint. The release workflow uses unpinned actions with broad write permissions, so its build hygiene warrants attention.

Latest 1.0.6

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing account is consistent with a user-owned project, but it also indicates a thin publishing base if that maintainer becomes unavailable.

Project backing

The package and repository are owned by the same individual account, providing clear ownership but no organizational backing to offset the thin maintainer base.

Release history

The package has had no release in over a year, after seven releases concentrated early in its roughly 20-month history. This suggests possible abandonment, despite the earlier rapid release cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This is the main abandonment concern for adopting the release.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.