conn/api

Release historydanger

Only two releases were published, with the latest in November 2018 and none in the last 12 months. This long release gap is a substantial abandonment concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in November 2018. This indicates maintenance has effectively stopped.

Maintainerscaution

One registry maintainer is responsible for publishing the package. That is a thin publishing base, although the linked repository identifies the same individual as its owner.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is reported. This is a modest maintenance and review gap rather than evidence of unsafe behavior by itself.

Security policycaution

The linked repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, with no provided evidence compensating for the gap.