beelab/mailchimp-bundle

Release historydanger

The latest release was in August 2016, about 10 years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment risk despite the nine-release history.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with the roughly 10-year release gap and providing no evidence of current maintenance.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the link provides weaker transparency about whether this source repository is specifically maintained for the published package.

Repo popularitycaution

The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these very low adoption signals provide little confidence that issues will be noticed or addressed.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a modest transparency gap, especially for a package that accesses an external API.