@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 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 |
v33.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.2.8
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.
v33.2.7
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.
v33.2.6
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.
v33.2.5
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.
v33.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.