@google-cloud/vertexai
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata-only signal, no behavioral change; consistent with legitimate Google publish pipeline variance. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.12.0 | 2 / 16 | |
| 1.11.0 | 2 / 16 | |
| 1.10.4 | 2 / 11 | |
| 1.10.3 | 2 / 11 | |
| 1.10.2 | 2 / 11 | |
| 1.10.0 | 1 / 11 | |
| 1.9.3 | 1 / 11 | |
| 1.9.2 | 1 / 11 | |
| 1.9.0 | 1 / 11 | |
| 1.8.1 | 1 / 11 | |
| 1.8.0 | 1 / 11 | |
| 1.7.0 | 1 / 11 | |
| 1.6.0 | 1 / 11 | |
| 1.5.0 | 1 / 11 | |
| 1.4.1 | 1 / 11 | |
| 1.4.0 | 1 / 11 | |
| 1.3.1 | 1 / 11 | |
| 1.3.0 | 1 / 11 | |
| 1.2.0 | 1 / 11 | |
| 1.1.0 | 1 / 11 | |
| 1.0.0 | 1 / 11 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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.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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.