hirokws/callkeeper

Release historydanger

The latest release was published more than nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, although the package is not deprecated.

Repo commit activitydanger

The repository recorded no commits or active maintainers in the last three months, consistent with a project whose last push was more than eight years ago. The repository is still available, but maintenance capacity appears very limited.

Maintainerscaution

Only one registry maintainer is listed, leaving little visible publishing redundancy. This is a moderate concern for continuity, though the repository is owned by the same individual and the package is small.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no external sign of active community support.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a hygiene gap rather than evidence that the release is unsafe.