@genkit-ai/core
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opentelemetry/exporter-jaeger | AI (phantom-deps): Newly added dep loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:body-parser | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic misfires for this framework package. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): cors is a declared runtime dependency; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:async-mutex | AI (phantom-deps): async-mutex is a declared runtime dependency; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): cors is a declared dependency of this package; the name similarity is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-metrics | AI (phantom-deps): Declared runtime dependency for OpenTelemetry metrics; stable false positive. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/context-async-hooks | AI (phantom-deps): Declared runtime dependency for OpenTelemetry context; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): Type-only dependency used for schema validation; stable false positive. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used to wrap dynamic import() for CJS compatibility, gated behind ENABLE_FIREBASE_MONITORING env var; not arbitrary code execution. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.36.0 | 20 / 9 | |
| 1.34.0 | 20 / 9 | |
| 1.33.0 | 20 / 9 | |
| 1.31.0 | 18 / 9 | |
| 1.27.0 | 19 / 8 | |
| 1.19.3 | 19 / 8 | |
| 1.16.1 | 18 / 8 | |
| 1.16.0 | 18 / 8 | |
| 1.15.2 | 18 / 8 | |
| 1.15.0 | 18 / 8 | |
| 1.14.0 | 18 / 8 | |
| 1.11.1 | 18 / 8 | |
| 1.8.0 | 18 / 8 |
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
2 findingsPackage name '@genkit-ai/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.