@llamaindex/liteparse
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep used for schema validation; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:unified | AI (phantom-deps): unified is a declared runtime dep for document processing; phantom-dep heuristic misfires here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.5.3 | 10 / 13 | |
| 1.5.2 | 10 / 13 | |
| 1.5.1 | 10 / 13 | |
| 1.5.0 | 10 / 13 | |
| 1.4.6 | 10 / 13 | |
| 1.4.5 | 10 / 13 | |
| 1.4.4 | 10 / 13 | |
| 1.4.3 | 10 / 13 | |
| 1.4.2 | 10 / 13 |
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.