@google-cloud/opentelemetry-cloud-monitoring-exporter
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@google-cloud/opentelemetry-resource-util | AI (dependencies): This is a sibling Google Cloud package from the same monorepo (GoogleCloudPlatform/opentelemetry-operations-js), published by the same trusted google-wombot publisher. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Google Cloud package published via google-wombot with strong track record; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.21.0 | 4 / 17 | |
| 0.20.0 | 4 / 18 | |
| 0.19.0 | 4 / 19 | |
| 0.18.0 | 4 / 19 | |
| 0.17.0 | 5 / 19 | |
| 0.16.0 | 5 / 18 | |
| 0.15.0 | 5 / 17 | |
| 0.14.0 | 4 / 18 | |
| 0.13.0 | 4 / 18 | |
| 0.12.0 | 4 / 18 | |
| 0.11.0 | 4 / 18 | |
| 0.10.0 | 4 / 18 | |
| 0.9.0 | 2 / 18 | |
| 0.8.0 | 2 / 17 | |
| 0.7.0 | 2 / 17 | |
| 0.6.0 | 2 / 17 | |
| 0.5.0 | 2 / 17 | |
| 0.4.3 | 2 / 17 | |
| 0.4.2 | 2 / 18 | |
| 0.4.1 | 7 / 13 | |
| 0.4.0 | 7 / 13 | |
| 0.3.0 | 6 / 12 |
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.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.
v0.18.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.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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.
v0.3.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.