voku/agent-kanban

This release appears suitable to depend on from a maintenance and transparency perspective: it is actively released, the repository was pushed very recently, the package is not deprecated or archived, and the artifact and repository contain substantial documentation, changelog, licensing, build configuration, and tests in the repository. The main reservations are that the project is young, commit activity is concentrated in one of two contributors, the repository has no reported security-scanning tooling, and one workflow grants top-level write permissions. These are meaningful but not disqualifying concerns, especially given the strong recent release and repository activity.

Latest 0.4.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, creating a publishing continuity concern; this is partly offset by active repository development but still leaves registry release authority concentrated.

Project backing

The repository is owned by an individual user rather than an organization, so the concentrated maintainer and commit activity represents a genuine individual-bus-factor concern.

Repo bus factor

The top contributor made 79 of 90 commits, or about 88%, and only two contributors were active; this concentration creates a real continuity risk, though the second contributor remains active.

Repo popularity

The repository has zero stars, forks, and watchers, indicating limited external adoption or review; popularity is supporting evidence rather than a decisive health verdict.

Repo tooling

Make and Composer provide build tooling, but no security-scanning tools were detected, leaving a security-process and maintenance-hygiene gap.