@blaxel/llamaindex
Blaxel SDK for TypeScript
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:llamaindex | AI (dependencies): llamaindex is the canonical LlamaIndex JS framework; stable dependency for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Package has 532 versions; rapid automated publishing is the established pattern for this package. | ai | |
| phantom-deps | phantom-dep:@llamaindex/mistral | AI (phantom-deps): @llamaindex/mistral is a declared runtime dependency used via config; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with clean track record; provenance absence is common and not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.2.90 | 9 / 4 | |
| 0.2.88 | 9 / 4 | |
| 0.2.78 | 9 / 4 | |
| 0.2.71 | 9 / 4 | |
| 0.2.63 | 9 / 4 | |
| 0.2.60 | 9 / 4 | |
| 0.2.42 | 9 / 4 | |
| 0.2.41 | 9 / 4 | |
| 0.2.25 | 9 / 4 | |
| 0.2.1 | 8 / 3 | |
| 0.2.0 | 8 / 3 |
v0.2.90
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ch.ploujoux) than the most recent previously approved version (cdrappier) on 2026-06-13, but ch.ploujoux is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.88
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ch.ploujoux) than the most recent previously approved version (cdrappier) on 2026-06-10, but ch.ploujoux is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.