@llamaindex/community
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 run-llama/LlamaIndexTS core team members. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation within same monorepo org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo sub-package with irregular publish cadence, no code changes accompany it. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 0.0.105 | 4 / 1 | |
| 0.0.104 | 4 / 1 | |
| 0.0.103 | 4 / 1 | |
| 0.0.102 | 4 / 1 | |
| 0.0.101 | 4 / 1 | |
| 0.0.100 | 4 / 1 | |
| 0.0.99 | 4 / 1 | |
| 0.0.98 | 4 / 1 | |
| 0.0.97 | 4 / 1 | |
| 0.0.96 | 4 / 1 | |
| 0.0.95 | 4 / 2 | |
| 0.0.94 | 4 / 2 | |
| 0.0.93 | 4 / 2 | |
| 0.0.92 | 4 / 2 | |
| 0.0.91 | 4 / 2 | |
| 0.0.90 | 4 / 2 | |
| 0.0.89 | 4 / 2 | |
| 0.0.88 | 4 / 2 | |
| 0.0.87 | 4 / 2 | |
| 0.0.86 | 4 / 2 | |
| 0.0.85 | 4 / 2 | |
| 0.0.84 | 4 / 2 | |
| 0.0.83 | 4 / 2 | |
| 0.0.82 | 4 / 2 | |
| 0.0.81 | 4 / 2 | |
| 0.0.80 | 4 / 2 | |
| 0.0.79 | 4 / 2 | |
| 0.0.78 | 4 / 2 | |
| 0.0.77 | 4 / 2 | |
| 0.0.76 | 4 / 2 | |
| 0.0.75 | 4 / 2 | |
| 0.0.74 | 4 / 2 | |
| 0.0.73 | 4 / 2 | |
| 0.0.72 | 4 / 2 | |
| 0.0.71 | 4 / 2 | |
| 0.0.70 | 4 / 2 | |
| 0.0.69 | 4 / 2 | |
| 0.0.68 | 4 / 2 | |
| 0.0.67 | 4 / 2 | |
| 0.0.66 | 4 / 2 | |
| 0.0.65 | 4 / 2 | |
| 0.0.64 | 4 / 2 | |
| 0.0.63 | 4 / 2 | |
| 0.0.62 | 4 / 2 | |
| 0.0.61 | 4 / 2 | |
| 0.0.60 | 4 / 2 | |
| 0.0.59 | 4 / 2 | |
| 0.0.58 | 4 / 2 | |
| 0.0.57 | 4 / 2 | |
| 0.0.56 | 4 / 2 | |
| 0.0.55 | 4 / 2 |
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
2 findingsThis version was published by a different npm account (cheesyfishes) than the most recent previously approved version (himself_65) on 2025-09-15. It has since remained available on npm for 306 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
2 findingsThis version was published by a different npm account (cheesyfishes) than the most recent previously approved version (himself_65) on 2025-09-11. It has since remained available on npm for 310 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.