@genesislcap/foundation-ai
Genesis Foundation AI - Provider-agnostic AI configuration and shared utilities
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
Versions (showing 11 of 120)
| Version | Deps | Published |
|---|---|---|
| 14.406.0 | 3 / 7 | |
| 14.405.0 | 3 / 7 | |
| 14.403.0 | 3 / 7 | |
| 14.402.1 | 3 / 7 | |
| 14.402.0 | 3 / 7 | |
| 14.401.4 | 3 / 7 | |
| 14.401.3 | 3 / 7 | |
| 14.401.2 | 3 / 7 | |
| 14.401.1 | 3 / 7 | |
| 14.401.0 | 3 / 7 | |
| 14.400.0 | 3 / 7 |
v14.406.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.405.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.403.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.402.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.402.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.401.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.401.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.401.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.401.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.401.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.400.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.