cac/autophing

Release historydanger

The latest release was in January 2016, with no releases in the last 12 months; this is strong evidence that maintenance has stopped despite 13 total releases.

Repo commit activitydanger

The repository has had zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and elevated abandonment risk.

Maintainerscaution

Only one registry account can publish releases. Organization backing provides some context, but the narrow publishing base still weakens continuity if that maintainer is unavailable.

Repo toolingcaution

The project uses Composer and Phing, showing a defined build process, but no security scanning tools were detected; this is a modest transparency and maintenance gap.

Repository archivedcaution

The repository is not archived, which leaves a possible path for future maintenance, but its last push was in June 2016 and does not offset the prolonged inactivity.