← Home

@syncfusion/ej2-compression

npm Homepage
6
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

syncfusionorgessentialjs2syncfusion-javascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

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

Version Deps Published
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

v33.1.44

1 finding
LOW No provenance attestation provenance

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

v32.2.3

2 findings
HIGH Publisher changed: essentialjs2 → syncfusion-javascript (on 2026-02-05) provenance

This version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v32.1.24

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.

v32.1.19

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.

v31.2.12

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.