avoo/elo

Release historydanger

The latest of only two releases was over 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository has had no commits and no active maintainers in the last 3 months, consistent with the long release hiatus. The repository being unarchived does not compensate for the lack of observed activity.

Repo issue activitycaution

There has been no issue or pull request activity recently, providing no evidence of ongoing maintenance or user support. With no recent releases or commits, this reinforces the abandonment concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a modest transparency and maintenance gap, not a standalone adoption blocker.

Security policycaution

The linked repository has no security policy. This weakens vulnerability-reporting transparency, although the package is small and the absence is less significant than its prolonged inactivity.