kk/chuck-command

Release historydanger

The latest release was published in January 2016, and there were no releases in the following 12 months of the collected history. This is strong evidence of abandonment risk despite eight historical releases.

Maintainerscaution

Only one registry account has publishing access, and the project backing signal identifies an individual repository owner rather than an organization. That leaves limited visible publishing redundancy.

Repo issue activitycaution

There are no open issues or pull requests and no recorded issue or pull-request activity in the last month. Combined with the old last push, this supports a conclusion of very limited current maintenance.

Repo popularitycaution

The repository has 7 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these very small numbers provide little evidence of an active user or contributor community.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a package that has been unchanged for years, the lack of visible security tooling weakens maintenance transparency.