@google-cloud/logging
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Official Google package; missing gitHead reflects publish-env change, not risk. | ai | |
| phantom-deps | phantom-dep:@grpc/grpc-js | AI (phantom-deps): @grpc/grpc-js is a declared dep used transitively via google-gax; stable false positive. | ai | |
| dependencies | unvetted-dep:eventid | AI (dependencies): eventid is a legitimate, purpose-built dependency used across Google Cloud Node.js libraries; no malicious history or concerns. | ai | |
| provenance | no-provenance | AI (provenance): Google Cloud official library published by google-wombot; absence of Sigstore provenance is not a meaningful risk signal for this well-established package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 11.3.0 | 16 / 38 | |
| 11.2.3 | 17 / 38 | |
| 11.2.2 | 17 / 38 | |
| 11.2.1 | 16 / 39 | |
| 11.2.0 | 16 / 39 | |
| 11.1.0 | 15 / 32 | |
| 11.0.0 | 15 / 32 |
v11.3.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.