← Home

@syncfusion/ej2-vue-richtexteditor

npm Repository Homepage

Essential JS 2 RichTextEditor component for Vue

36
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

syncfusionorgessentialjs2syncfusion-javascript

Keywords

vue-rich-text-editorvue-html-editorvue-markdown-editorvue-wysiwyg-editor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): syncfusion-javascript is the established Syncfusion org account with 175 approved packages; transition from essentialjs2 is a documented org migration. ai
provenance no-provenance AI (provenance): Syncfusion does not use Sigstore provenance; consistent across all their packages. ai

Versions (showing 36 of 36)

Version Deps Published
34.1.32 3 / 0
34.1.30 3 / 0
34.1.29 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.48 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.15 3 / 0
31.2.12 3 / 0
31.2.10 3 / 0
31.2.5 3 / 0

v34.1.32

1 finding
INFO No provenance attestation provenance

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

v34.1.30

1 finding
INFO No provenance attestation provenance

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

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.

v33.2.13

1 finding
INFO No provenance attestation provenance

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