@genkit-ai/google-cloud
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): node-fetch is declared in package.json dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 1.40.1 | 19 / 12 | |
| 1.40.0 | 19 / 12 | |
| 1.39.0 | 19 / 12 | |
| 1.38.0 | 18 / 9 | |
| 1.37.0 | 18 / 9 | |
| 1.36.0 | 18 / 9 | |
| 1.35.0 | 18 / 9 | |
| 1.34.0 | 18 / 9 | |
| 1.33.0 | 18 / 9 | |
| 1.32.0 | 18 / 9 | |
| 1.31.0 | 18 / 9 | |
| 1.30.1 | 18 / 9 | |
| 1.29.0 | 18 / 9 | |
| 1.28.0 | 18 / 9 | |
| 1.27.0 | 18 / 9 | |
| 1.26.0 | 18 / 9 | |
| 1.25.0 | 17 / 9 | |
| 1.24.0 | 17 / 9 | |
| 1.23.0 | 17 / 9 | |
| 1.22.0 | 17 / 9 | |
| 1.21.0 | 17 / 9 | |
| 1.20.0 | 17 / 9 | |
| 1.19.3 | 17 / 9 | |
| 1.19.2 | 17 / 9 | |
| 1.19.1 | 17 / 9 | |
| 1.19.0 | 17 / 9 | |
| 1.18.0 | 17 / 9 | |
| 1.17.1 | 17 / 9 | |
| 1.17.0 | 17 / 9 | |
| 1.16.1 | 17 / 9 | |
| 1.16.0 | 17 / 9 | |
| 1.15.5 | 17 / 9 | |
| 1.15.4 | 17 / 9 | |
| 1.15.2 | 17 / 9 | |
| 1.15.1 | 17 / 9 | |
| 1.15.0 | 17 / 9 | |
| 1.14.1 | 17 / 9 | |
| 1.14.0 | 17 / 9 | |
| 1.13.0 | 17 / 9 | |
| 1.12.0 | 17 / 9 | |
| 1.11.1 | 17 / 9 | |
| 1.11.0 | 17 / 9 | |
| 1.10.0 | 17 / 9 | |
| 1.9.0 | 17 / 9 | |
| 1.8.0 | 17 / 9 | |
| 1.7.0 | 17 / 9 | |
| 1.6.2 | 17 / 9 | |
| 1.6.1 | 17 / 9 | |
| 1.6.0 | 17 / 9 | |
| 1.5.0 | 17 / 9 | |
| 1.4.0 | 17 / 9 | |
| 1.3.0 | 17 / 9 | |
| 1.2.0 | 17 / 9 | |
| 1.1.0 | 17 / 9 | |
| 1.0.5 | 17 / 9 | |
| 1.0.4 | 17 / 9 |
v1.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.