@llamaindex/core
LlamaIndex Core Module
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known LlamaIndex team accounts. | ai | |
| provenance | publisher-changed | AI (provenance): Handoff to himself65, the repo owner; legitimate maintainer transition. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Types package loaded by convention; stable FP. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @llamaindex/core is a legitimate scoped package in the LlamaIndex ecosystem; the 1-edit distance to 'cors' is coincidental and not a typosquat. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.6.23 | 5 / 4 | |
| 0.6.22 | 5 / 4 | |
| 0.6.21 | 5 / 4 | |
| 0.6.20 | 5 / 4 | |
| 0.6.19 | 5 / 4 | |
| 0.6.18 | 5 / 4 | |
| 0.6.17 | 5 / 4 | |
| 0.6.16 | 5 / 4 | |
| 0.6.15 | 5 / 4 | |
| 0.6.14 | 5 / 4 | |
| 0.6.13 | 5 / 4 | |
| 0.6.12 | 5 / 4 | |
| 0.6.11 | 5 / 4 | |
| 0.6.10 | 5 / 4 | |
| 0.6.9 | 5 / 4 | |
| 0.6.8 | 5 / 4 | |
| 0.6.7 | 5 / 4 | |
| 0.6.6 | 5 / 4 | |
| 0.6.5 | 5 / 4 | |
| 0.6.4 | 5 / 4 | |
| 0.6.3 | 5 / 4 | |
| 0.6.2 | 5 / 5 | |
| 0.6.1 | 5 / 5 | |
| 0.6.0 | 5 / 5 | |
| 0.5.8 | 5 / 5 | |
| 0.5.7 | 5 / 5 | |
| 0.2.4 | 4 / 6 | |
| 0.2.2 | 3 / 6 | |
| 0.2.1 | 3 / 6 | |
| 0.2.0 | 3 / 4 | |
| 0.1.12 | 3 / 4 | |
| 0.1.11 | 3 / 4 | |
| 0.1.10 | 3 / 4 | |
| 0.1.9 | 3 / 3 | |
| 0.1.8 | 3 / 3 | |
| 0.1.7 | 3 / 3 | |
| 0.1.6 | 3 / 3 | |
| 0.1.5 | 3 / 3 | |
| 0.1.4 | 3 / 3 | |
| 0.1.3 | 3 / 2 | |
| 0.1.2 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.1.0 | 3 / 2 | |
| 0.0.3 | 3 / 2 | |
| 0.0.2 | 3 / 1 | |
| 0.0.1 | 3 / 1 |
v0.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
2 findingsThis version was published by a different npm account than previous versions on 2024-09-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2024-09-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2024-09-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2024-09-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
2 findingsThis version was published by a different npm account than previous versions on 2024-09-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
2 findingsThis version was published by a different npm account than previous versions on 2024-09-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
2 findingsThis version was published by a different npm account than previous versions on 2024-09-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
2 findingsThis version was published by a different npm account than previous versions on 2024-08-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
2 findingsThis version was published by a different npm account than previous versions on 2024-08-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
2 findingsThis version was published by a different npm account than previous versions on 2024-08-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
2 findingsThis version was published by a different npm account than previous versions on 2024-07-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
2 findingsThis version was published by a different npm account than previous versions on 2024-07-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findingsThis version was published by a different npm account than previous versions on 2024-07-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsThis version was published by a different npm account than previous versions on 2024-07-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
2 findingsThis version was published by a different npm account than previous versions on 2024-07-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsThis version was published by a different npm account than previous versions on 2024-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
2 findingsThis version was published by a different npm account than previous versions on 2024-07-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
2 findingsThis version was published by a different npm account than previous versions on 2024-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
2 findingsThis version was published by a different npm account than previous versions on 2024-07-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.