← Home

@llamaindex/liteparse

41
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

emanuelclferreirapreston-runllamayongparkzhaotaicle-does-thingscheesyfishesdisiokadrianlyjak

Keywords

pdfparserocrtext-extractionpdf-to-textdocument-parsing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 41 of 41)

Version Deps Published
2.10.0 1 / 3
2.9.0 1 / 3
2.8.1 1 / 3
2.8.0 1 / 3
2.7.0 1 / 3
2.6.0 1 / 3
2.5.1 1 / 3
2.5.0 1 / 3
2.4.1 1 / 3
2.4.0 1 / 3
2.3.0 1 / 3
2.2.1 1 / 3
2.2.0 1 / 3
2.1.2 1 / 3
2.1.1 1 / 3
2.1.0 1 / 3
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
1.4.1 10 / 13
1.4.0 10 / 13
1.3.2 10 / 13
1.3.1 10 / 13
1.3.0 10 / 13
1.2.0 10 / 13
1.1.0 10 / 13
1.0.1 9 / 13
1.0.0 9 / 13

v2.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.9.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.8.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.7.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.6.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.