@syncfusion/ej2-pdf-data-extract
This repository provides advanced support for data extraction from PDF documents
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN license | AI (license): Syncfusion commercial EULA; expected for all versions of this vendor's packages. | ai | |
| source-diff | encoded-string-file:src/pdf-data-extract/core/text-extraction/font-utils.js | AI (source-diff): Base64 font glyph data present in source, matches function purpose. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): openjpeg.wasm is a JPEG2000 decoder needed for PDF image extraction. | ai | |
| source-diff | encoded-string-file:dist/es6/ej2-pdf-data-extract.es2015.js | AI (source-diff): Long base64 are embedded OTF font blobs in _getFontEncodedString(); stable across every release of this PDF library. | ai | |
| source-diff | encoded-string-file:dist/es6/ej2-pdf-data-extract.es5.js | AI (source-diff): Same embedded font base64 as es2015 build, ES5 target. Recurring benign pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/ej2-pdf-data-extract.umd.min.js | AI (source-diff): Same as above — UMD minified bundle from Syncfusion's build pipeline, stable pattern across versions. | ai | |
| source-diff | encoded-string-file:dist/global/ej2-pdf-data-extract.min.js | AI (source-diff): Standard minified output from Syncfusion's build pipeline; long strings are base64/binary data for PDF processing, not malicious payloads. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-compression | AI (phantom-deps): Same-org Syncfusion dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@syncfusion/ej2-base | AI (phantom-deps): Same-org Syncfusion dependency; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 34.1.32 | 3 / 0 | |
| 34.1.31 | 3 / 0 | |
| 34.1.30 | 3 / 0 | |
| 34.1.29 | 3 / 0 | |
| 33.2.15 | 3 / 0 | |
| 33.2.13 | 3 / 0 | |
| 33.2.12 | 3 / 0 | |
| 33.2.10 | 3 / 0 | |
| 33.2.8 | 3 / 0 | |
| 33.2.7 | 3 / 0 | |
| 33.2.6 | 3 / 0 | |
| 33.2.5 | 3 / 0 | |
| 33.2.4 | 3 / 0 | |
| 33.2.3 | 3 / 0 | |
| 33.1.49 | 3 / 0 | |
| 33.1.47 | 3 / 0 | |
| 33.1.46 | 3 / 0 | |
| 33.1.45 | 3 / 0 | |
| 33.1.44 | 3 / 0 | |
| 32.2.9 | 3 / 0 | |
| 32.2.8 | 3 / 0 | |
| 32.2.7 | 3 / 0 | |
| 32.2.5 | 3 / 0 | |
| 32.2.4 | 3 / 0 | |
| 32.2.3 | 3 / 0 | |
| 32.1.25 | 3 / 0 | |
| 32.1.24 | 3 / 0 | |
| 32.1.23 | 3 / 0 | |
| 32.1.22 | 3 / 0 | |
| 32.1.21 | 3 / 0 | |
| 32.1.20 | 3 / 0 | |
| 32.1.19 | 3 / 0 | |
| 31.2.18 | 3 / 0 | |
| 31.2.16 | 3 / 0 | |
| 31.2.15 | 3 / 0 | |
| 31.2.12 | 3 / 0 | |
| 31.2.10 | 3 / 0 | |
| 31.2.5 | 3 / 0 |
v34.1.32
3 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.31
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.30
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.1.29
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.1.45
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-03-24, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v33.1.44
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-03-16, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.2.9
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-03-10, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.2.8
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-03-03, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.2.7
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-02-24, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.2.5
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-02-17, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.2.4
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-02-11, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.2.3
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-02-05, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.25
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-01-27, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.24
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-01-20, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.23
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-01-13, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.22
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2026-01-06, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.21
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2025-12-30, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.20
4 findingsModified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2025-12-23, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v32.1.19
5 findingsPackage contains compiled binaries that could be backdoors: • dist/openjpeg/openjpeg.wasm
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 175 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (syncfusion-javascript) than the most recent previously approved version (essentialjs2) on 2025-12-16, but syncfusion-javascript is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v31.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.