@google-cloud/pubsub
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): google-wombot is Google's official publishing bot; lack of Sigstore provenance is expected for this publisher and does not indicate risk. | ai | |
| phantom-deps | phantom-dep:@types/duplexify | AI (phantom-deps): @types/duplexify is a TypeScript type package used as a runtime dep in Google Cloud libraries for type compatibility; this is a stable pattern for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): google-wombot is Google's official publishing bot with a strong track record; major version bumps (v3→v4) can appear as dormancy gaps. Not indicative of account takeover. | ai | |
| phantom-deps | phantom-dep:@types/long | AI (phantom-deps): @types/long is a TypeScript type package used as a runtime dep in Google Cloud libraries for type compatibility; this is a stable pattern for this package. | ai | |
| dependencies | unvetted-dep:google-gax | AI (dependencies): google-gax is Google's own gRPC/API client framework, a core dependency of all Google Cloud Node.js client libraries. Stable and expected for this package. | ai | |
| dependencies | unvetted-dep:@google-cloud/precise-date | AI (dependencies): @google-cloud/precise-date is a Google Cloud utility package, a standard dependency for this library across versions. | ai | |
| dependencies | unvetted-dep:heap-js | AI (dependencies): heap-js is a well-known data structure library used for message ordering in pubsub; legitimate and expected dependency. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): @opentelemetry/semantic-conventions is a legitimate runtime dep used for OpenTelemetry tracing integration; the phantom-dep finding is a false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 15 / 39 | |
| 5.2.4 | 15 / 39 | |
| 5.2.3 | 15 / 39 | |
| 5.2.2 | 15 / 39 | |
| 5.2.1 | 15 / 39 | |
| 5.2.0 | 15 / 39 | |
| 5.1.0 | 15 / 39 | |
| 5.0.0 | 14 / 40 | |
| 4.11.0 | 14 / 40 | |
| 4.10.0 | 14 / 40 | |
| 4.9.0 | 14 / 40 | |
| 4.8.0 | 14 / 40 | |
| 4.7.2 | 14 / 39 | |
| 4.7.1 | 14 / 37 | |
| 4.7.0 | 14 / 37 | |
| 4.6.0 | 14 / 36 | |
| 4.5.0 | 14 / 36 | |
| 4.4.1 | 14 / 36 | |
| 4.4.0 | 14 / 36 | |
| 4.2.0 | 16 / 36 | |
| 4.0.3 | 16 / 36 | |
| 3.7.3 | 16 / 35 |
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
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.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.