wtsvk/evitadb-php-client

Lifecycle scriptscaution

A post-autoload-dump install lifecycle script is present, so installation executes project code beyond ordinary file extraction. No script behavior was provided to show whether this is necessary or safe.

Repo bus factorcaution

Two contributors split recent commits evenly, so activity is not concentrated in one person. The contributor count is still small, limiting resilience if either stops contributing.

Repo popularitycaution

The repository has no stars, forks, or watchers. Popularity is only supporting evidence, so this lowers confidence in community depth but is not decisive for a young specialized client.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a transparency and maintenance gap, not evidence of unsafe code by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. That is a real transparency gap for a client that connects to a database service.