tigress/google_api

Repo commit activitycaution

The repository records zero commits and zero active maintainers during the last three months, a meaningful maintenance concern despite the recent push and strong registry release cadence.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the link between the published package and its source is not clearly demonstrated.

Repo popularitycaution

The repository has zero stars and forks and one watcher, providing little external adoption evidence; this is supporting caution only, not proof that the package is unsafe or abandoned.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected; this is a modest transparency and maintenance gap for a library handling API integrations.

Security policycaution

The repository has no security policy. For a small package this is not independently severe, but it leaves vulnerability-reporting expectations undocumented.