truegenics/aweber

Release historydanger

Only one release exists, published about 9 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk for a library intended for ongoing API integration.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long gap since the sole release and providing no evidence of active maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Low adoption is supporting evidence of limited project maturity, but it is outweighed by the direct maintenance signals rather than decisive on its own.

Repo toolingcaution

Composer and Phing provide build tooling, but no security scanning tools are configured. That weakens transparency around ongoing maintenance practices.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a hygiene gap, though not by itself evidence that the package is unsafe.