@cnakazawa/watch

Release historydanger

The latest release was published over six years ago, with only two releases overall and none in the last 12 months. This is the strongest sign of possible abandonment, despite the package remaining available.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months. Combined with the old latest release, this materially raises abandonment risk.

Maintainerscaution

A single registry publishing account is a thin release surface, although the repository and package name match and the project is user-owned, so this is a modest resilience concern rather than a severe risk.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while 43 issues and 16 pull requests remain open. This suggests unresolved maintenance needs.

Repo toolingcaution

The repository has no build tooling or security scanning configured. This lowers transparency and automated assurance, although the small, simple file tree limits the significance of the gap.