googleapis/google-cloud-go

What this is

This repository publishes the official Go packages for calling Google Cloud Platform services. Each service gets its own import path under cloud.google.com/go, for example cloud.google.com/go/firestore or cloud.google.com/go/storage, so Go applications can create typed clients rather than hand-building HTTP requests. It is aimed at Go developers who are building on or integrating with Google Cloud, from App Engine and Cloud Functions to Cloud Run and external servers.

Quick start

1. Install the package for the service you need, replacing firestore with the target package:

go get cloud.google.com/go/firestore@latest

2. Create a client. Inside a Google Cloud environment such as Compute Engine, Kubernetes Engine, or App Engine, Application Default Credentials are picked up automatically:

client, err := storage.NewClient(ctx)

3. When running locally, set up user credentials with gcloud auth application-default login from the Google Cloud CLI, which Application Default Credentials will detect automatically. To use a service account key file instead, set GOOGLE_APPLICATION_CREDENTIALS to the key path or pass option.WithCredentialsFile to NewClient.

The released API list and per-package reference documentation are the place to confirm the exact service you plan to call: reference docs and the Go package index.

Constraints

• The libraries target the two most recent major Go releases; the README currently lists Go 1.26 and Go 1.27.
• Authentication is required: either a Google Cloud runtime with an attached identity or locally configured Application Default Credentials or an explicit service account key.
• Some packages are still under development and may make backward-incompatible changes.
• Access to the underlying services and their quotas is governed by Google Cloud, not by this client library.

HotRepo's take

The repository appeared once in the Go weekly ranking on 2026-11-10, at 20th place with 2 stars gained in that period, and it has no recorded position on the all-language daily chart. That single snapshot is not enough to describe a trend. What the record does show is the profile of a long-lived, slow-moving official SDK: created in 2014, with 4,553 stars and 1,605 forks, and very small weekly net growth. The practical weight of the project is in its breadth of service coverage and its versioning and authentication model, which matter more to users than ranking movement.