@editorjs/editorjs
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:codex-notifier | AI (dependencies): Long-standing runtime dep from the same CodeX org; present across many approved versions of this package. | ai | |
| phantom-deps | phantom-dep:@editorjs/caret | AI (phantom-deps): Same-org dependency; likely bundled into dist rather than directly imported in source. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.31.6 | 3 / 32 | |
| 2.31.5 | 3 / 32 | |
| 2.31.4 | 3 / 32 | |
| 2.31.3 | 3 / 32 | |
| 2.31.2 | 3 / 32 | |
| 2.31.1 | 3 / 32 | |
| 2.31.0 | 3 / 32 |
v2.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.