debiprasad/oauth2-avaza

Release historydanger

Only two releases were published, with the latest about eight years ago and none in the last 12 months. This is strong evidence that maintenance has stopped.

Repo commit activitydanger

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

Maintainerscaution

The registry lists one maintainer, and project_backing identifies a personal user-owned repository rather than organizational backing. This leaves limited visible maintenance capacity.

Repo popularitycaution

The repository has one star, no forks, and one watcher. Popularity is only supporting evidence, but these values provide little external evidence of ongoing use or review.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap, though it is less significant than the package's prolonged inactivity.