@genkit-ai/ai No license 36 versions

@genkit-ai/ai

npm Repository Homepage

36

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pavelgji2amsamapascal07google-wombot

Keywords

genkitaigenaigenerative-ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped Google package; Levenshtein match to 'hapi' is a false positive.	ai	2026/05/27
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped Google package; Levenshtein match to 'pg' is a false positive.	ai	2026/05/27
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped Google package; Levenshtein match to 'qs' is a false positive.	ai	2026/05/27
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped Google package; Levenshtein match to 'joi' is a false positive.	ai	2026/05/27
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped Google package; Levenshtein match to 'ajv' is a false positive.	ai	2026/05/27
phantom-deps	phantom-dep:colorette	AI (phantom-deps): Used in build/logging config; stable false positive for this package.	ai	2026/05/27
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): Type-only dependency; framework-scoped, not directly imported at runtime.	ai	2026/05/27
phantom-deps	phantom-dep:@opentelemetry/api	AI (phantom-deps): Telemetry API used via convention/config; stable false positive for this package.	ai	2026/05/27

Versions (showing 36 of 36)

Version	Deps	Published
1.34.0	11 / 8	2026-05-12
1.33.0	11 / 8	2026-04-24
1.30.1	10 / 8	2026-03-13
1.29.0	10 / 8	2026-02-20
1.28.0	10 / 8	2026-01-22
1.27.0	10 / 8	2025-12-19
1.26.0	10 / 8	2025-12-12
1.25.0	10 / 8	2025-12-03
1.24.0	10 / 8	2025-11-18
1.23.0	10 / 8	2025-11-13
1.22.0	10 / 8	2025-10-28
1.21.0	10 / 8	2025-10-06
1.20.0	10 / 8	2025-09-26
1.19.3	10 / 8	2025-09-19
1.19.2	10 / 8	2025-09-09
1.19.1	10 / 8	2025-09-08
1.19.0	10 / 8	2025-09-08
1.18.0	10 / 8	2025-08-29
1.17.1	10 / 8	2025-08-24
1.17.0	10 / 8	2025-08-22
1.16.1	10 / 8	2025-08-12
1.16.0	10 / 8	2025-08-07
1.15.5	10 / 8	2025-07-25
1.15.4	10 / 8	2025-07-25
1.15.2	10 / 8	2025-07-21
1.15.1	10 / 8	2025-07-18
1.15.0	10 / 8	2025-07-17
1.14.1	10 / 8	2025-07-10
1.14.0	10 / 8	2025-06-27
1.13.0	9 / 7	2025-06-19
1.12.0	9 / 7	2025-06-06
1.11.1	9 / 7	2025-06-02
1.11.0	9 / 7	2025-05-30
1.10.0	9 / 6	2025-05-21
1.9.0	9 / 6	2025-05-14
1.8.0	9 / 6	2025-05-05

v1.34.0

1 finding

LOW No provenance attestation provenance

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

v1.33.0

1 finding

LOW No provenance attestation provenance

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

v1.30.1

1 finding

LOW No provenance attestation provenance

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

v1.29.0

1 finding

LOW No provenance attestation provenance

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

v1.28.0

1 finding

LOW No provenance attestation provenance

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

v1.27.0

1 finding

LOW No provenance attestation provenance

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

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.0

1 finding

LOW No provenance attestation provenance

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

v1.24.0

1 finding

LOW No provenance attestation provenance

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

v1.23.0

1 finding

LOW No provenance attestation provenance

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

v1.22.0

1 finding

LOW No provenance attestation provenance

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

v1.21.0

1 finding

LOW No provenance attestation provenance

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

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.19.3

1 finding

LOW No provenance attestation provenance

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

v1.19.2

1 finding

LOW No provenance attestation provenance

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

v1.19.1

1 finding

LOW No provenance attestation provenance

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

v1.19.0

1 finding

LOW No provenance attestation provenance

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

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.1

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.1

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.5

1 finding

LOW No provenance attestation provenance

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

v1.15.4

1 finding

LOW No provenance attestation provenance

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

v1.15.2

1 finding

LOW No provenance attestation provenance

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

v1.15.1

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.1

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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