gts/kata

This release is usable but carries meaningful maturity and maintenance uncertainty. It is a very new v0.1.1 package with only two releases, no observed commit activity or active maintainers in the measured three-month window, no tests or changelog, and no security policy or scanning tooling. Those concerns are partly contextualized by the repository being freshly pushed, the package having a matching and README-referencing repository, a clear MIT license, a small runtime dependency profile, no deprecation, and no install-time lifecycle scripts. Adopt it only if you can tolerate an early-stage CLI whose maintenance track record is not yet established.

Latest v0.1.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The artifact contains a coherent small CLI structure with source files, an executable, Composer metadata, and a README, but the 20-file tree includes no tests or development documentation.

Package scaffolding

A substantive README documents this CLI and its usage, but both the artifact and repository lack tests and a changelog. For an early-stage project this is a real maintenance and verification gap.

Project backing

The repository is owned by an individual user rather than an organization. This is not inherently unhealthy, but it means there is no provided organizational backing to compensate for the otherwise thin maintenance history.

Release history

The package is effectively brand new, with an age of 0 days and only 2 releases; this provides too little history to establish mature release practices or long-term maintenance.

Repo commit activity

The measured three-month window shows 0 commits and 0 active maintainers. The repository's recent push partly explains this because the project is newly published, but there is still no demonstrated ongoing maintenance history.