rekasso/contact

Release historydanger

Only two releases exist, both from November 2019, and there have been no releases in nearly seven years. This is strong evidence of abandonment risk for a package intended for application integration.

Maintainerscaution

The package has one registry maintainer, and the project backing is an individual account rather than an organization. A single-person maintenance base leaves limited capacity for fixes or continuity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the past month. Combined with the nearly seven-year release gap, this supports a conclusion of inactive maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these counters provide no supporting evidence of a wider maintainer or user community.

Security policycaution

The linked repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is less serious than evidence of active security problems.