← Home

@tailor-cms/ce-jodit-html-edit

npm

Tailor CMS Jodit HTML editor authoring component

10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

droguljicee_adminikovacundersc0perkusan00

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped @tailor-cms package with 9 versions, 424-day history, and author linking to the tailor-cms GitHub org. Missing README/repo metadata is a packaging style issue, not a security signal. ai
phantom-deps phantom-dep:lodash-es AI (phantom-deps): lodash-es is a declared runtime dependency; the phantom-dep finding reflects indirect usage patterns in a build tool context, not a security concern. ai

Versions (showing 10 of 10)

Version Deps Published
2.0.1 3 / 9
2.0.0 3 / 9
0.1.0 2 / 7
0.0.8 2 / 7
0.0.7 2 / 7
0.0.6 3 / 7
0.0.5 3 / 7
0.0.4 3 / 7
0.0.3 3 / 7
0.0.1 2 / 7

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.