@syncfusion/ej2-compression
7
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
syncfusionorgessentialjs2syncfusion-javascript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate org-level publisher rotation within @syncfusion scope; new account has 230 approved packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Syncfusion publishes in batch release cycles; dormancy reflects their release cadence, not abandonment. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Syncfusion library component; sparse README/keywords is consistent across the entire ej2 suite. | ai | |
| provenance | no-provenance | AI (provenance): Syncfusion does not publish with Sigstore provenance; consistent across all ej2 packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 34.1.29 | 1 / 0 | |
| 33.2.3 | 1 / 0 | |
| 33.1.44 | 1 / 0 | |
| 32.2.3 | 1 / 0 | |
| 32.1.24 | 1 / 0 | |
| 32.1.19 | 1 / 0 | |
| 31.2.12 | 1 / 0 |
v34.1.29
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.