@ai-sdk/llamaindex
This package contains a LlamaIndex adapter for the AI SDK.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Vercel org migrated from vercel-release-bot to GitHub Actions for publishing; SLSA attestation confirms CI/CD continuity. | ai |
Versions (showing 10 of 320)
| Version | Deps | Published |
|---|---|---|
| 1.0.96 | 1 / 4 | |
| 1.0.95 | 1 / 4 | |
| 1.0.94 | 1 / 4 | |
| 1.0.93 | 1 / 4 | |
| 1.0.92 | 1 / 4 | |
| 1.0.91 | 1 / 4 | |
| 1.0.90 | 1 / 4 | |
| 1.0.89 | 1 / 4 | |
| 1.0.88 | 1 / 4 | |
| 1.0.87 | 1 / 4 |
v1.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.