@editorjs/embed
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established official Editor.js plugin; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@editorjs/editorjs | AI (dependencies): This is the core Editor.js runtime; a direct dependency for an official Editor.js plugin is expected and benign. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 1 / 17 | |
| 2.7.7 | 1 / 21 | |
| 2.7.6 | 1 / 21 | |
| 2.7.5 | 1 / 21 | |
| 2.7.4 | 1 / 21 | |
| 2.7.2 | 0 / 14 |
v2.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.