← Home

@syncfusion/ej2-blockeditor

npm Repository Homepage

Feature Rich Block Editor control with built in support editing, formatting content.

7
Versions
SEE LICENSE IN license
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

Keywords

ej2syncfusionblockeditorblockseditornotionmodular-editorblock-basedinline-editor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@syncfusion/ej2-lists AI (phantom-deps): Syncfusion monorepo pattern; transitive deps used by bundled components. ai
phantom-deps phantom-dep:@syncfusion/ej2-buttons AI (phantom-deps): Syncfusion monorepo pattern; transitive deps used by bundled components. ai
phantom-deps phantom-dep:@syncfusion/ej2-notifications AI (phantom-deps): Syncfusion monorepo pattern; transitive deps used by bundled components. ai

Versions (showing 7 of 7)

Version Deps Published
33.2.10 10 / 0
33.2.8 10 / 0
33.2.7 10 / 0
33.2.6 10 / 0
33.2.5 10 / 0
33.2.4 10 / 0
33.2.3 10 / 0

v33.2.10

1 finding
LOW No provenance attestation provenance

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

v33.2.8

1 finding
LOW No provenance attestation provenance

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

v33.2.7

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.

v33.2.6

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.

v33.2.5

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.

v33.2.4

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.

v33.2.3

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.