rindow/rindow-module-google-cloud

Release historydanger

Only two releases appeared, both in April 2020, and none were published in the last 12 months despite the package being over six years old. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the unchanged release history and indicating no observed ongoing maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides little supporting evidence of an active user or contributor community.

Repo toolingcaution

Composer is used for builds, but no security scanning tools were detected. The missing scanning reduces maintenance and supply-chain visibility.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself show the package is unsafe.