@google-cloud/common-grpc

Common components for Cloud APIs Node.js Client Libraries that require gRPC

@google-cloud/common-grpc@1.0.10 was published on 2020-01-15. Its manifest declares 10 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.10.0.

All @google-cloud/common-grpc versions · Permanent reference to 1.0.10

Package specifications

Version1.0.10
License declarationApache-2.0
Published2020-01-15T18:00:44.102Z
Node.js requirement>=8.10.0
Type declarationsBundled declarations
Runtime dependency count10
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size85.28 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entry./build/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies101
Repository stars11
Repository forks9

Install @google-cloud/common-grpc 1.0.10

npm install @google-cloud/common-grpc@1.0.10
pnpm add @google-cloud/common-grpc@1.0.10
yarn add @google-cloud/common-grpc@1.0.10

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Maintained0/10 — project is archived
Code-Review9/10 — Found 23/25 approved changesets -- score normalized to 9
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness