@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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Package is a napi-rs native module; bundling .node and .so is the expected distribution pattern for this package. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Major rewrite from JS to Rust/NAPI; JS source replaced by native binary — size drop is expected and explained. | ai | |
| 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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.0.8 | 1 / 3 | |
| 2.0.7 | 1 / 3 | |
| 2.0.5 | 1 / 3 | |
| 2.0.4 | 1 / 3 | |
| 2.0.3 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 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 |
v2.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.7
2 findingsPackage contains compiled binaries that could be backdoors: • liteparse.linux-x64-gnu.node • libpdfium.so
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.5
2 findingsPackage contains compiled binaries that could be backdoors: • liteparse.linux-x64-gnu.node • libpdfium.so
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.4
2 findingsPackage contains compiled binaries that could be backdoors: • liteparse.linux-x64-gnu.node • libpdfium.so
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
2 findingsPackage contains compiled binaries that could be backdoors: • liteparse.linux-x64-gnu.node • libpdfium.so
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
2 findingsPackage contains compiled binaries that could be backdoors: • liteparse.linux-x64-gnu.node • libpdfium.so
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
2 findingsPackage contains compiled binaries that could be backdoors: • liteparse.linux-x64-gnu.node • libpdfium.so
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.