gufy/mailchimp

Release historydanger

The latest release was published in November 2016, with no releases in the last 12 months and only two releases overall. This strongly raises abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.

Repo popularitycaution

The repository has only 2 stars and 1 fork. This is supporting evidence of limited adoption, but it is not decisive because popularity alone does not determine health.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, especially alongside the lack of recent activity.

Security policycaution

No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a real but secondary gap compared with the prolonged inactivity.