conn/entity

Release historydanger

The last release was over seven years ago, with no releases in the past 12 months. Its 114 historical releases show prior activity but do not offset the prolonged inactivity.

Repo commit activitydanger

The repository has recorded zero commits and zero active maintainers in the past three months, consistent with a project that has not been maintained since February 2019.

Maintainerscaution

Only one registry account has publishing access, leaving little visible maintainer redundancy. The linked repository is user-owned rather than organization-backed, so this thin base is a meaningful continuity concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap, though it is less serious than the prolonged lack of maintenance.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This adds transparency risk alongside the long maintenance gap.