← Home

@editorjs/dom

npm Repository
3
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

codex-team

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped @editorjs package; not a typosquat of koa. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped @editorjs package; not a typosquat of got. ai
typosquat typosquat.levenshtein:jsdom AI (typosquat): Scoped @editorjs package; not a typosquat of jsdom. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @editorjs package; not a typosquat of joi. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @editorjs package; not a typosquat of zod. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.0 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

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.