← Home

@genkit-ai/vertexai

56
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pavelgji2amsamapascal07google-wombot

Keywords

genkitgenkit-plugingenkit-embeddergenkit-modelgoogle cloudvertex aiimagenimage-generationgeminigoogle geminigoogle aiaigenaigenerative-ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:tests/modelgarden/v2/anthropic_test.ts AI (source-diff): Base64 string is a JPEG test image fixture in a test file, not a malicious payload. ai
provenance no-provenance AI (provenance): Google Genkit packages consistently publish without Sigstore provenance; stable false positive for this publisher. ai

Versions (showing 56 of 56)

Version Deps Published
1.40.1 9 / 10
1.40.0 9 / 10
1.39.0 9 / 10
1.38.0 9 / 10
1.37.0 9 / 10
1.36.0 9 / 10
1.35.0 9 / 10
1.34.0 9 / 10
1.33.0 9 / 10
1.32.0 9 / 10
1.31.0 9 / 10
1.30.1 9 / 10
1.29.0 9 / 10
1.28.0 9 / 10
1.27.0 9 / 10
1.26.0 9 / 10
1.25.0 9 / 10
1.24.0 9 / 10
1.23.0 9 / 10
1.22.0 9 / 10
1.21.0 9 / 7
1.20.0 9 / 7
1.19.3 9 / 7
1.19.2 9 / 7
1.19.1 9 / 7
1.19.0 9 / 7
1.18.0 9 / 7
1.17.1 9 / 7
1.17.0 9 / 7
1.16.1 9 / 7
1.16.0 9 / 7
1.15.5 9 / 7
1.15.4 9 / 7
1.15.2 9 / 7
1.15.1 9 / 7
1.15.0 9 / 7
1.14.1 9 / 7
1.14.0 9 / 7
1.13.0 9 / 7
1.12.0 9 / 7
1.11.1 9 / 7
1.11.0 9 / 7
1.10.0 9 / 7
1.9.0 11 / 7
1.8.0 11 / 7
1.7.0 11 / 7
1.6.2 11 / 7
1.6.1 11 / 7
1.6.0 11 / 7
1.5.0 11 / 7
1.4.0 11 / 7
1.3.0 11 / 7
1.2.0 11 / 7
1.1.0 11 / 7
1.0.5 11 / 7
1.0.4 11 / 7

v1.40.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.40.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.39.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.