tendoo/cloud-breeze

Release historydanger

The last registry release was over six years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package intended as an active Laravel framework extension.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates a severe abandonment risk.

Dependency profilecaution

The package declares 11 runtime dependencies and no development dependencies. This is a relatively broad runtime surface, increasing maintenance burden, but it is not by itself evidence that the release is unsafe to depend on.

Repo issue activitycaution

The repository has 29 open pull requests, with no new or merged pull requests in the last month. That backlog and lack of movement reinforce the maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a framework package with authentication, API, and dashboard code, this is a meaningful hygiene gap.