vitorfba/laravel-evolution-client

Maintainerscaution

Only one account has registry publishing access, which limits release-account redundancy. However, repository activity shows a second active contributor, partly reducing the maintenance concern.

Project backingcaution

The package and repository are both owned by the same individual account, so the source relationship is clear. Individual ownership provides less organizational maintenance redundancy than an organization-backed project.

Release historycaution

The project is only 56 days old and has three releases, with releases clustered within about one hour. That shows initial activity but provides limited long-term maintenance evidence.

Repo issue activitycaution

There were no new or closed issues and no pull requests in the last month. With a young repository this is ambiguous rather than evidence of abandonment, though it provides little external maintenance signal.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool is reported. The missing scanner is a transparency gap, not evidence that the package is unsafe or unmaintained.