arnoson/kirby-deploy

Usable with caveats: it is actively released and clearly backed by a matching repository, but it is still early-stage with no tests or changelog and only one recent repository contributor. Review deployment behavior carefully before adopting it for production sites.

Latest 0.4.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. That is a limited publishing safety net for a user-owned project, though repository activity provides additional evidence of ongoing maintenance.

Package scaffolding

The artifact and repository include a substantial README and the repository uses GitHub Releases, but neither contains tests or a changelog. For a deployment tool, the absence of tests is a meaningful maintenance and reliability gap.

Repo bus factor

All one recent commit came from a single contributor, leaving a low recent contributor base. Because the repository is user-owned rather than organization-owned, there is no project-backing evidence to offset this concentration.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer. Recent registry releases compensate for some of this weakness, but the repository's current development activity is thin.

Repo issue activity

There are only two open issues, with no issues or pull requests opened or closed in the last month. This is not abandonment evidence by itself, but it provides little evidence of active community maintenance.