tatter/accounts

Release historydanger

The last release was over six years ago, with no releases in the past 12 months. This strongly raises abandonment risk, although the package reached a stable v1.0.4 release.

Repo commit activitydanger

The repository recorded no commits and no active maintainers during the past three months, consistent with the multi-year release gap. This is strong evidence that maintenance has stopped.

Lifecycle scriptscaution

A post-update-cmd lifecycle script runs during Composer updates, adding some installation-time behavior that consumers should understand. The signal does not show that the script is harmful, so this is a limited concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. That is a modest hygiene gap rather than evidence that the release is unsafe.

Repository archivedcaution

The repository is not archived, which leaves open the possibility of future maintenance. Its last push was still over six years ago, so the unarchived status only partly offsets the inactivity evidence.