google-gax
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): uuid is a well-established, widely-trusted npm package. Its addition to google-gax is a legitimate dependency for UUID generation in an API client library. | ai | |
| provenance | missing-githead | AI (provenance): google-gax is a high-trust Google package published via automation (google-wombot); missing gitHead reflects a CI pipeline change, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): google-wombot publishes many packages without Sigstore attestation; this is a process gap, not a malicious signal for this well-established Google package. | ai | |
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is a standard, widely-used protobuf library and an expected dependency for a Google API client library handling gRPC/protobuf. No security concerns. | ai | |
| phantom-deps | phantom-dep:@types/long | AI (phantom-deps): @types/* packages are type declarations not directly imported at runtime; phantom-dep finding is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@types/long | AI (dependencies): @types/long is a standard TypeScript type definition for the long library, appropriate as a runtime dep for a gRPC/protobuf package that exposes types to consumers. | ai | |
| dependencies | unvetted-dep:proto3-json-serializer | AI (dependencies): proto3-json-serializer is a Google-maintained protobuf serialization package, directly relevant to google-gax's purpose. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): node-fetch is a legitimate HTTP library; declared as a dep and used indirectly or in fallback browser builds, consistent with google-gax's architecture. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is a legitimate file cleanup utility; its presence as a declared dep without direct import is a build/tooling pattern consistent with this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.0.6 | 11 / 37 | |
| 5.0.5 | 11 / 37 | |
| 5.0.4 | 10 / 37 | |
| 5.0.3 | 11 / 37 | |
| 5.0.1 | 11 / 37 | |
| 5.0.0 | 12 / 37 | |
| 4.3.5 | 12 / 35 | |
| 4.3.3 | 12 / 35 | |
| 4.3.1 | 12 / 35 | |
| 4.2.0 | 12 / 35 | |
| 4.0.5 | 11 / 34 | |
| 4.0.1 | 11 / 35 |
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
v4.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.